Hi, this is a very old topic, so that might explain why you didn’t get a prompt answer the first time. Old topics like this are full of information that’s out of date, so often we like to start fresh with a new one. But now that we’re here, let’s see what we can do about the HOV ramps.
This looks like the area you’re experiencing problems with:
As far as I can tell, these ramps are tagged as:
motor_vehicle=no, which keeps car routers from using the ramps in general- hov=designated`, which overrides that restriction for HOVs only
hov:minimum=2, which specifies that only vehicles with two or more people count as HOV (as opposed to some of the higher minimums WSDOT sometimes posts)
These tags should be enough to prevent a routing engine from sending cars down the ramp unless it happens to know the user qualifies as an HOV. For example, using the main OSM website, we can see that Valhalla avoids this ramp by default using the community-developed car profile.
If your Tesla is routing you down the ramp anyways, it probably isn’t respecting the hov=designated tag (which is somewhat less common in the U.S.). Or it might not even be using OSM data for this purpose. Some data consumers only use OSM data for the base map, or only for routing, or only for a subset of the navigation data, such as speed limits or parking aisles. Reportedly, Tesla does use the Valhalla routing engine, but this doesn’t necessarily mean they use the same profile or data.
Unfortunately, it’s hard to know the exact cause of the behavior you’re seeing, since Tesla has been tight-lipped about any use of OSM. But if you know of any other ramps that OSM might have mistagged, at least we can ensure correctness for users of other software or hardware.
