Submitted by Cooking_with_MREs t3_126pvmm in washingtondc
ctrlqwertydj t1_jeab7uf wrote
I can’t believe how dysfunctional the new fare gates are. This new bottlenecking exit/entrance issue is one Metro created directly 😢
toorigged2fail t1_jeac7q9 wrote
I haven't had an issue... what station(s)?
Wheresmycardigan t1_jeam8b0 wrote
The Google pay/apple pay NFC takes a few seconds to read but people are so used to tapping and instant walking thru that it causes mis read and then back up.
[deleted] t1_jeanzxk wrote
[removed]
toorigged2fail t1_jeb6wlk wrote
Ah I don't use NFC. Hitting interferes with my building fob that I have stickered to my phone
Wheresmycardigan t1_jebbqdt wrote
Apple or android?
My phone defaults to Google wallet but Metro is able to detect and pull up smart trip, but there's a lag in the read by the fare reader.
My building access for the office is also via app, so Bluetooth doesn't interfere bc readers are able to differentiate NFC signals.
All I need now is a newer model car that can start via my phone lol
toorigged2fail t1_jebkcxe wrote
I think I tried to close, but currently Android
sprint113 t1_jebcxy0 wrote
The new gate arms swing faster, which ironically makes them slower. The old gates would allow like 4-5 people through without closing-reopening if they tapped fast enough. I don't think I've see that on the new gates, though it's possible it's because the ridership at my exit station has gone down a bit, more people are paying by app and lots of people just hop the gate.
Wheresmycardigan t1_jebfdov wrote
That's a good point. During peak office rush hour if people had the right timing cadence right behind each other, fare gate wouldn't even need to close until after a good number people passed thru
[deleted] t1_jeac9et wrote
[removed]
Viewing a single comment thread. View all comments