dunno said:
The only issue I really have with Arc is that the tap on/off function is more awkward than basically any other tap card I've used. You often have to hold the card on the reader for a good second or two, which wastes time for impatient riders/drivers, and there's semi-regularly issues with even getting it to read at all. I never have this issue with any other tap card, from Tokyo to Los Angeles. It's a quick swipe and read.

This is admittedly a relatively mild complaint in the grand scheme of things.
Click to expand...
Depending upon how busy it is and if I am getting on or off, I will just tap and keep moving. In particular if it's busy or I am getting off. More often than not I will then get the beep a second or two later that everything is alright. Boarding, I will do a quick tap but will usually linger long enough for the response from the reader. I don't think there's a need to hold the card to the reader until you get a response. I cringe a little bit when I see people pressing their cards against the readers hard enough to make the card very noticeably bend. I often find that stationary readers (LRT stations) respond almost instantly, which I guess is the difference between a hardwire connection and a wireless connection.
 
EdwardEdm said:
Depending upon how busy it is and if I am getting on or off, I will just tap and keep moving. In particular if it's busy or I am getting off. More often than not I will then get the beep a second or two later that everything is alright. Boarding, I will do a quick tap but will usually linger long enough for the response from the reader. I don't think there's a need to hold the card to the reader until you get a response. I cringe a little bit when I see people pressing their cards against the readers hard enough to make the card very noticeably bend. I often find that stationary readers (LRT stations) respond almost instantly, which I guess is the difference between a hardwire connection and a wireless connection.
Click to expand...

Fair enough. I just don't want to deal with it not actually beeping. And why doesn't it just, you know, beep if it's reading at that moment, like literally every other tap card?
 
Ah, should have been clearer. I'm referring to information, data, you know, items that are used to target a specific market. Data is money, I won't even get into thatt "tracking" information argument...
That type of data information would be great for fare zones calculation efforts, but I don't feel like being on the receiving end of unsolicited marketing. Yeah, I'm wearing my aluminum hat rather tightly these days
 
IMG_1734.png

Girders have been installed over the Henday?
 
How has the LRT been during this coldsnap and snow? I am aware of supposedly a technical issue last night around 5:30 where the trains were stopped at either Boonie Doon and/or Davies for 25 minutes before the trains started heading south. Once it did get going, I was under the impression that the train did not go all the way to millwoods but stopped at the 2nd to last stop and people had to walk to the millwoods transit centre.
 
It's currently -25 outside, and the Valley Line LRT is still humming along. Just wait until the weekend though! 🥶

1704932264126.png
 
According to someone on facebook there was a problem on the southern portion of the line, something that the train was stuck to Grey Nuns or something.
 
Barnaby said:
I see what you are saying now. If you control for the differences, it would put the 2 car Valley Line train at 743 passengers?, so just shy of the capacity of the current SD160s of 760 in a 4 car arrangement.
Click to expand...

Yes. Granted, the Valley line vehicles have less row seating, if the high floor vehicles follow suit then that difference widens some more.

For reference, I was using the LRT design guidelines which lists the AW2 capacity of the SD-160 at 146 pax, lower than the U2 capacity of 160 pax.
 
You must log in or register to post here.

Back
Top