attheyard wrote: This is exactly why I don't understand the I66 setup-if you get on I66 inside the beltway as a non-HOV driver, you WILL be fined. There is a cop sitting at every exit checking cars. Driving east on 66, there is a split in the road where you can either continue on 66 (but the entirety of 66 is now HOV), or you can exit onto the beltway around the city.
Just to clarify for those that don't drive on I-66 nearly every day like I do...There are electronic message signs and metal printed signs that tell you the rules at the entry points. BUT you have to actually read the signs. They look like this:
attheyard wrote: The beltway around the city is almost never faster, but you have to do it if you're alone in the car. Waze doesn't know this. So why is I66 left as a routing option?
This is not quite true as it depends on where you are going. If you are going TO DC, it's a lot different than if you are going AROUND DC. I would never downtown if going from Fairfax to Annapolis, the beltway is always faster if traffic is moving at speed. But if going to DC before or after the HOV restriction time, I would take I-66 as it is faster.
There are a lot of details to consider here but I think these HOV routes need to be an available option. Can these options be setup in waze so whenever you request a route that potentially includes one of these HOV routes you are presented with at least two options INSTEAD OF defaulting to the one fastest route? My OEM Ford GPS system presents two options as the default and lets you pick.