CBenson wrote:But HOT lanes should not be mapped as PLR. You want those who are willing to pay the toll to be able to route over them. There is no reason not have them set to tolled freeway type now so that they can be used for routing.
I don't see any reason to map HOV lanes as PLR at this point. Where appropriate to map them, just map them with the appropriate HOV restriction. However, no-one will be routed over a segment with a HOV restriction. So there is really no reason to spend much effort at this point to change HOV lanes previously mapped as PLRs to freeway (or highway) type with HOV restrictions.
kentsmith9 wrote:In the SF Bay Area we have 7 toll bridges which provide virtually the only access to those locations on the other side of the water, so everyone pays the toll. In the stretches of freeways leading to the bridges we have HOT lanes that drivers are not willing to pay due to the limited benefit. So a user who lives in the bay area will leave the Toll route option on all the time to enable bridge crossing, but then would be continuously routed in HOT lanes.
CBenson wrote:I agree that is a problem and you may have do something different in the SF Bay Area. But that is a permanent issue. We can't account for both drivers that want to use some toll roads and drivers that want to use all the toll roads. This will remain an issue even after the HOV indication is enabled in the client.
CBenson wrote:However even if I have avoid toll routes selected, waze will route through toll segments in some instances. For long routes over 100 miles or so I get an error if the only non-toll route is too circuitous on low road types. But for shorter commuting type trip lengths, waze simply gives me a toll route even if I have avoid tolls selected and there is not a reasonable alternative.
Users browsing this forum: No registered users