Mike-1323 wrote:So, after a couple of weeks of the HOT lanes being open along the VA side of the beltway the UR's are pouring in. I put the HOT lanes on the map and have them all set as Freeway with Toll and ramps without. Should this be changed? The wiki recommendation is to make HOV lanes as parking lot roads. Should the new HOT lanes be changed to parking lot roads?
That would prevent the average user from being routed onto the HOT lanes. Many of the UR's are due to users being routed onto the toll Express lanes because they have not checked the avoid toll box in the routing options. With the HOT lanes as PLR the routing server should never route onto the express lanes. The problem is that, due to routing auto-lock and gps error, the users that actually use the express lanes will be getting routing directions from the main travel lanes and will have incorrect exit instructions. (this is currently happening on the I95 HOV lanes in northern VA)
There just doesn't seem to be a good solution.
I'm a NOVA native/resident and regular user of the beltway but I do not use it every day for commuting. There is another thread where we've been discussing the 495 Express Lanes and I'm not sure if you saw that discussion.
If someone is complaining about being routed onto the Express Lanes and they have not checked the box to avoid toll lanes, I would say... This is by design. If the 495ELs are the fastest route and are marked as a toll road, then waze is working as designed (just like any other GPS system). If you changed the ELs to a PRL as you suggest then anyone who uses the lanes regularly would have to manually select that route every time (if I understand the system correctly). I'm pretty confident that the majority of 495EL users are regular users/locals and not just passing through. The problem you describe is a sufficient reason to keep it as is.
Can we add some sort of warning/popup that warns the user that the given route contains a toll (it may already, I can't remember) and/or add the word TOLL to the EL lanes name so it is more obvious(it may already)? I think this is sufficient warning that you are on a toll road.
How do we handle the NJ Turn Pike? It is the same thing. When driving from Baltimore to Philly, there are several parallel routes; some with toll and some without. How do you warn wazers that they have been directed onto a toll road there?
This begs another question...When waze suggests one route over another how much time data it is using? Does waze compare minutes only or minutes and seconds? Does it give preference to a shorter (distance-wise) route if it is one minute slower because it keeps you on a main highway. For example, If waze suggests the 495ELs because it saves me 30 seconds over the regular lanes and it costs me $2, it wasn't worth it (I'm not in the top 1%). I know waze doesn't know what the toll is but I want the choice. Give me the information (travel times) and let me choose if I want to pay the toll to save time.
A similar situation happened to me recently. I was using waze to get to a local address. Distance was about 7 miles of back streets, no highways (15 minutes). It is an area I know well. I took a turn against waze's suggested route that I thought was better and the ETA immediately improved by two minutes. Why would waze suggest this slower route? Yes, I have FASTEST selected.
I think I made this suggestion before but I think it's a good one. Every time waze gives a route that contains a toll have it go to the routes choice screen and force the user to choose the toll route or the non-toll route. The toll is marked, the wazer has all the information they need.