I was mulling this announcement and article last night and I am relieved that drivers with riders in their vehicle will not pay the proposed congestion pricing of $19-$23 peak toll, which is proposed for once a day. That being said, I wholeheartedly agree with the Lyft statement: how does the rideshare company know whether or not you alr…
I was mulling this announcement and article last night and I am relieved that drivers with riders in their vehicle will not pay the proposed congestion pricing of $19-$23 peak toll, which is proposed for once a day. That being said, I wholeheartedly agree with the Lyft statement: how does the rideshare company know whether or not you already paid your congestion pricing for the day and, more importantly, let’s say they do figure out a way to find out this information, do you now only match riders in the outer boros with drivers that already paid their daily congestion price so as to not charge the passenger? Does that mean drivers who didn’t pay their daily congestion price will be like the ugly red-headed stepchild and not get any rides because the rider would have to pay an extra $19-$23?
On a privacy level, do I want rideshare companies knowing my driving patterns by having access to information on my EZ-PASS account because if they need to know whether or not I was Manhattan, they will have that information. I see it as the start of an encroachment into information I may not want rideshare companies to have access to. If we start this process of giving out EZ-PASS information, what is to stop rideshare companies from knowing whether or not you were paid already to enter New Jersey, for example. If I was paid $20 bridge/tunnel toll by Uber to go from NYC to NJ and now (due to sharing of EZ-PASS information) Lyft knows they don’t have to pay me $20 to go back into NYC, but I need that $20 if only because the NJ rideshare rates are too low and it helps add to my earnings.
Think you're making a lot of great points re. complications around practically executing this plan or how that would work. Perhaps the E-ZPass system would someone be programmed to only charge TLC plates once per day and then prevent that plate from being charged again somehow (e.g., the system is programmed something along the lines of (IF T555555C = BILLED, DON'T BILL, BILL). It's looking like the drivers will be on the hook for the tolls though as not sure how it could be divided among passengers / trips across multiple apps / trip prices, throughout a 24 hour period.
The E-ZPass privacy point is one we didn't appreciate and it's interesting to consider, although we think Uber/Lyft already have a ton of data re. driver movements. We also think it's noteworthy for the MTA to clarify whether this would be only NYC FHVs (e.g. TLC regulated FHVs) or ALL FHVs that can enter City - that can have a lot of different impacts (e.g., Newark Taxis), which might benefit TLC-licensed vehicles.
NYC Congestion Pricing is a big moment for the industry, let's see how this plays out. Perhaps a total exemption is granted, you never no, given taxis / FHVs are already paying per trip congestion surcharges (e.g., still feels like this is a bit of double taxation).
I was mulling this announcement and article last night and I am relieved that drivers with riders in their vehicle will not pay the proposed congestion pricing of $19-$23 peak toll, which is proposed for once a day. That being said, I wholeheartedly agree with the Lyft statement: how does the rideshare company know whether or not you already paid your congestion pricing for the day and, more importantly, let’s say they do figure out a way to find out this information, do you now only match riders in the outer boros with drivers that already paid their daily congestion price so as to not charge the passenger? Does that mean drivers who didn’t pay their daily congestion price will be like the ugly red-headed stepchild and not get any rides because the rider would have to pay an extra $19-$23?
On a privacy level, do I want rideshare companies knowing my driving patterns by having access to information on my EZ-PASS account because if they need to know whether or not I was Manhattan, they will have that information. I see it as the start of an encroachment into information I may not want rideshare companies to have access to. If we start this process of giving out EZ-PASS information, what is to stop rideshare companies from knowing whether or not you were paid already to enter New Jersey, for example. If I was paid $20 bridge/tunnel toll by Uber to go from NYC to NJ and now (due to sharing of EZ-PASS information) Lyft knows they don’t have to pay me $20 to go back into NYC, but I need that $20 if only because the NJ rideshare rates are too low and it helps add to my earnings.
Think you're making a lot of great points re. complications around practically executing this plan or how that would work. Perhaps the E-ZPass system would someone be programmed to only charge TLC plates once per day and then prevent that plate from being charged again somehow (e.g., the system is programmed something along the lines of (IF T555555C = BILLED, DON'T BILL, BILL). It's looking like the drivers will be on the hook for the tolls though as not sure how it could be divided among passengers / trips across multiple apps / trip prices, throughout a 24 hour period.
The E-ZPass privacy point is one we didn't appreciate and it's interesting to consider, although we think Uber/Lyft already have a ton of data re. driver movements. We also think it's noteworthy for the MTA to clarify whether this would be only NYC FHVs (e.g. TLC regulated FHVs) or ALL FHVs that can enter City - that can have a lot of different impacts (e.g., Newark Taxis), which might benefit TLC-licensed vehicles.
NYC Congestion Pricing is a big moment for the industry, let's see how this plays out. Perhaps a total exemption is granted, you never no, given taxis / FHVs are already paying per trip congestion surcharges (e.g., still feels like this is a bit of double taxation).