Quote:
Originally Posted by Kisai
An "as the crow flies" fare would be impossible. The closest you get is 13KM by car.
It would be completely fair to charge a "point to point" fare as long as the transit system could calculate that, however in all likeliness, the system would track the tap-in/tap-out event (or tap-in on return trip) as a return trip to determine how many stops were traveled, and thus the km's.
A "per km" flat fare also disproportionately punishes Surrey and Langley, mostly for reasons self-inflicted by Surrey.
|
My main concern for distance-based fare is that it will completely kill off the attractiveness of transit service in more rural area with less services. It is more suited for city with more population and more ridership that supports point-to-point or grid-based service, as oppose to the transfer-based system that's used in most places outside of CoV. If a transfer will increase fare, nobody will take transit if the bus doesn't take them to their destination in a single ride (as if that transfer did not put-off most of the potential riders) and eventually it will not be feasible to run most of the feeder routes as no one want to pay that much and the service will eventually die off. Beside my example above, there are a few other examples I can think of:
- Speed vs. distance - A 30min ride in City of Vancouver may only crawl 5km, while a 30min ride in the suburb may get you 20km - it's the same 30min ride, but you need to pay $2.20 for one and $4.30 for the other?
- Distance to destination - If you live in the inner city, you may be able to do all your errands within a 5km radius, while in suburb it may be 10km as everything is further apart. Therefore, transit is more expensive in the suburb than in the city for the same trip purpose, even though TransLink said they want to build ridership there?
- Multiple destinations along similar path - using the old 159-169-177 as an example - people from Coquitlam (A) wants to go to SilverCity (1) on Lougheed, and also want to go to the casino (2) in United Blvd; people from Port Coquitlam (B) also wants to go to the same place -- how many routes they must provide?
Initially there were 3 - the 169 (A-1), the 159 (B-1), and the 177 (A-2). People who wants B-2 can take a transfer between 159 and 177.
They then see this as service duplication, and adjust to 169 (A-1), 159 (B-2), and cancel the 177, telling people who wants B-1 and A-2 to transfer at Braid or PoCo/Coquitlam.
Then people complains so they make the 159 (A-B-2) to reduce that transfer for A-2.
How would they do it for distance based fare? Now no one wants to take 159 for A-2 as it means they will pay $1.50 more, no one wants to transfer at Braid as it would almost a max fare for such a little trip within the same city. For people in PoCo it is also an extra charge for going through Coquitlam. Should they reinstate the 3rd or even add the 4th route to avoid overcharging people? That could be doable if they make both the 159 and 169 shuttle - eventually you don't even need a conventional bus anymore! Or just focus on the two most popular route and tell the other 30% of the rider to get lost, or add a transfer point between the 159 and 169 and tell 100% of the people to pay a bit extra for the added trip length? And then you add in that Riverview detour -- it's only $0.25 extra for those poor 169 riders, right? Or should they split the 169 again into 2 routes? Maybe there should also be a "159 express" that goes straight down Shaughnessey to skip Citadel Heights. And then split both routes again so one branch goes to (1) and the other goes to (2). Now we're talking about 8 routes instead of 2.
This is exactly how they would do in a non-transfer based system. But then they may have a few hundred riders per day for each type of service, and we have probably no more than 50.
That can be solved if they ignore the transfer point and charge base on the "as the crow flies" fare. But what if someone finish their errand and get back home within 90min - now the distance is 0 km regardless of how far you actually go?