![]() ![]() ![]() |
|
sbiddle: You can't easily have a topup done when tagging on to a bus in Wellington for example, since any updates could only be loaded onto the bus at night when it goes back to the depot the the data is synced.
sbiddle: Anybody know what HOP's plans are for online topups? It's something very few places around the world offer, in part because you can only do it when you've got terminals with backhaul.
With Oyster for example your balance can only be updates at tube station barriers and some bus stops. You can't easily have a topup done when tagging on to a bus in Wellington for example, since any updates could only be loaded onto the bus at night when it goes back to the depot the the data is synced.
Staying in Wellington. Check out my AirBnB in the Wellington CBD. https://www.airbnb.co.nz/rooms/32019730 Mention GZ to get a 10% discount
System One: PS3 SuperSlim, NPVR and Plex Server running on Intel NUC (C2D) (Windows 10 Pro), Sony BDP-S390 BD player, Pioneer AVR, Odroid C2 running Kodi and Plex, Panasonic 60" 3D plasma, Samsung Q80 Atmos soundbar. Google Chromecast, Google Chromecast TV
System Two: Oppo BDP-80 BluRay Player with hardware mode to be region free, Vivitek HD1080P 1080P DLP projector with 100" screen, Denon AVRS730H 7.2 Channel Dolby Atmos/DTS-X AV Receiver, Samsung 4K player, Google Chromecast, Odroid C2 running Kodi and Plex
sxz: I have my HOP card but am now waiting for it to roll out on my bus.
I understand from a colleague that the card needs to be removed from your wallet, and the sensor is not particularly powerful (i.e. you cant just wave your wallet in front of the sensor)?
Is this true? Can this be fixed?
sxz: I have my HOP card but am now waiting for it to roll out on my bus.
I understand from a collegue that the card needs to be removed from your wallet, and the sensor is not particularly powerful (i.e. you cant just waive your walllet infront of the sensor)?
Is this true? Can this be fixed?
graemeh:sbiddle: You can't easily have a topup done when tagging on to a bus in Wellington for example, since any updates could only be loaded onto the bus at night when it goes back to the depot the the data is synced.
I don't see any technical reason why not. The balance is held on the card and you could just update the card. The bus reader already updates the available balance each time you get on and off.
I doubt you'd want to do it though, one of the big advantages of the slapper card is it is fast. Doing topups on the bus would cause delays.
sxz: I have my HOP card but am now waiting for it to roll out on my bus.
I understand from a collegue that the card needs to be removed from your wallet, and the sensor is not particularly powerful (i.e. you cant just waive your walllet infront of the sensor)?
Is this true? Can this be fixed?
Surely the whole point of the system is speed and ease, like the oyster card.
Also, it sounds like you are all saying a snapper card can work interchangable with a hop card now, but it wont be the case in a few months time (when phase 2 rolls out). Will this mean in phase 2 a hop card can be used to buy a can of coke but snapper wont buy a bus trip?
Cheers,
*confused*
sbiddle:
Because buses don't have high bandwidth realtime connectivity this can't easily be done - data with Snapper is updated each time the bus enters a depot. With Oyster or Octopus for example the prime use is trains where entry/exit barriers have realtime connectivity and can apply online updates to the card virtually instantly.
There is also the issue of minimising the transaction process and keeping this below ~500ms, if lots is going on such as balance updates this can be a challenge.
Staying in Wellington. Check out my AirBnB in the Wellington CBD. https://www.airbnb.co.nz/rooms/32019730 Mention GZ to get a 10% discount
System One: PS3 SuperSlim, NPVR and Plex Server running on Intel NUC (C2D) (Windows 10 Pro), Sony BDP-S390 BD player, Pioneer AVR, Odroid C2 running Kodi and Plex, Panasonic 60" 3D plasma, Samsung Q80 Atmos soundbar. Google Chromecast, Google Chromecast TV
System Two: Oppo BDP-80 BluRay Player with hardware mode to be region free, Vivitek HD1080P 1080P DLP projector with 100" screen, Denon AVRS730H 7.2 Channel Dolby Atmos/DTS-X AV Receiver, Samsung 4K player, Google Chromecast, Odroid C2 running Kodi and Plex
lchiu7:sbiddle:
Because buses don't have high bandwidth realtime connectivity this can't easily be done - data with Snapper is updated each time the bus enters a depot. With Oyster or Octopus for example the prime use is trains where entry/exit barriers have realtime connectivity and can apply online updates to the card virtually instantly.
There is also the issue of minimising the transaction process and keeping this below ~500ms, if lots is going on such as balance updates this can be a challenge.
I think the data on the buses is retrieved from the bus when it's in the depot so they can update the card balances in the back end. This isn't so much so that they know you have enough money to use the card next time (because the buses don't do realtime validation) but to know enough to send emails to those who have registered warning them of low balances. Also the transaction information is used to update the data warehouse.
sbiddle:lchiu7:sbiddle:
Because buses don't have high bandwidth realtime connectivity this can't easily be done - data with Snapper is updated each time the bus enters a depot. With Oyster or Octopus for example the prime use is trains where entry/exit barriers have realtime connectivity and can apply online updates to the card virtually instantly.
There is also the issue of minimising the transaction process and keeping this below ~500ms, if lots is going on such as balance updates this can be a challenge.
I think the data on the buses is retrieved from the bus when it's in the depot so they can update the card balances in the back end. This isn't so much so that they know you have enough money to use the card next time (because the buses don't do realtime validation) but to know enough to send emails to those who have registered warning them of low balances. Also the transaction information is used to update the data warehouse.
Yip, that's what it's used for now.
Online topups can't work necause this isn't real time. If Snapper wanted to launch online topups now for example the Snapper terminal would only be able to update your card balance after the bus has visited a depot and been able to sync it's data.
Regards,
Old3eyes
old3eyes:sbiddle:lchiu7:sbiddle:
Because buses don't have high bandwidth realtime connectivity this can't easily be done - data with Snapper is updated each time the bus enters a depot. With Oyster or Octopus for example the prime use is trains where entry/exit barriers have realtime connectivity and can apply online updates to the card virtually instantly.
There is also the issue of minimising the transaction process and keeping this below ~500ms, if lots is going on such as balance updates this can be a challenge.
I think the data on the buses is retrieved from the bus when it's in the depot so they can update the card balances in the back end. This isn't so much so that they know you have enough money to use the card next time (because the buses don't do realtime validation) but to know enough to send emails to those who have registered warning them of low balances. Also the transaction information is used to update the data warehouse.
Yip, that's what it's used for now.
Online topups can't work necause this isn't real time. If Snapper wanted to launch online topups now for example the Snapper terminal would only be able to update your card balance after the bus has visited a depot and been able to sync it's data.
Why can't they be set up to sync data at the end of each run as they seem to stand for at least 10 minutes + at each end of their trip..
sbiddle:old3eyes:sbiddle:lchiu7:sbiddle:
Because buses don't have high bandwidth realtime connectivity this can't easily be done - data with Snapper is updated each time the bus enters a depot. With Oyster or Octopus for example the prime use is trains where entry/exit barriers have realtime connectivity and can apply online updates to the card virtually instantly.
There is also the issue of minimising the transaction process and keeping this below ~500ms, if lots is going on such as balance updates this can be a challenge.
I think the data on the buses is retrieved from the bus when it's in the depot so they can update the card balances in the back end. This isn't so much so that they know you have enough money to use the card next time (because the buses don't do realtime validation) but to know enough to send emails to those who have registered warning them of low balances. Also the transaction information is used to update the data warehouse.
Yip, that's what it's used for now.
Online topups can't work necause this isn't real time. If Snapper wanted to launch online topups now for example the Snapper terminal would only be able to update your card balance after the bus has visited a depot and been able to sync it's data.
Why can't they be set up to sync data at the end of each run as they seem to stand for at least 10 minutes + at each end of their trip..
Because that's not a solution. A bus might only return to the depot once or twice a day. What happens when you're sitting at home, top up online and then head out to the bus? Your credit can't be applied.
Regards,
Old3eyes
|
![]() ![]() ![]() |