I’ve seen a few users now have trouble coming across the bridge and the while clearly they came across the bridge and stayed on the top deck, Waze then thinks they are below the bridge and able to turn on a side street. In reality, they can’t turn off the top deck of the bridge.
Is this just a function of GPS and Waze not keeping them on the “same” street?
Thanks for any help.
My take, in looking the link over, is that there is probably something askew with the elevations in the area. Given the complexity there, that wouldn’t be surprising, and I know at least 6 elevations are in use there. The roads/offramps stack as many as 4 deep as far as genuine physical elevation goes, and what is on top in one stack can be a layer or two down in a stack nearby - it’s a recipe for mismatch. Also plausible is that there is a junction in the mix somewhere there shouldn’t be.
Disclaimer: I haven’t done a fully detailed analysis of every facet of the elevations here - just enough to get the complexity and how many elevations are in use. I’ve done a little bit of work with elevations, but, to date at least, nothing remotely this complex.
This post is old enough that I’m not sure if it’s been addressed outside of this forum. If it continues to be a repeating problem, ping me in PM and I’ll try and find the time to comb through the details of it.
So here’s my take on it. https://www.waze.com/editor/?env=usa&lon=-122.66145&lat=45.51692&layers=1925&zoom=8&segments=41062470 was set to elevation Ground. So is the ground level street under the bridge. When drivers used the ramp they were forced to keep left due to traffic. Understandable. Since they kept to the left of the other segment, and they were on the same elevation as the other segment, they may be snapped to the other segment. I changed that ramp to elevation 1 to match the bridge elevation. If that doesn’t solve it I’d suggest pulling the Morrison Street ground level segments north of the bridge segments.
Keep in mind that Elevation only prevents Waze from generating MPs thinking that the roads should be connected. All of the URs I’ve seen here that showed the Waze route had directed them to take the Water Ave exit but they had missed it for whatever reason. When they stay on the bridge, their GPS track doesn’t get far enough off-route to recalculate (and if it did, there’s a 50/50 change they’d get snapped to the ground segments).
I can imagine the GPS having a very low accuracy rate at this point too given how many things are going on, so the changes of a errant recalc seems higher than average.
Thanks for everyone’s responses and the ramp elevation level change. I haven’t seen this issue pop up in the last week or so, but it happened multiple times before that. I’ll post something here again if I see this issue again for consideration of the other solutions proposed.
Thanks!
Hmm, for some reason I thought you were talking about the segments to the north (Morrison). It would appear I didn’t do anything for your particular problem. Sorry for the confusion.
My understanding is the same as FzNk, the elevation of two sections need to be different so the application doesn’t try to connect them. It doesn’t matter for routing if an s-in is elevation 4 and an s-out is elevation -2. Provided the switch occurs at a junction.
My guess is that the GPS is being erratic and Waze reconnects them on the ground level road because the GPS track for both roads (top and bottom) are the same, but they generally seem to be more abundant along the north edge of the street.
If it continues, my suggested fix would be to move SE Belmont (the higher elevation mH) to the north side of the street as show on the satellite photo and switch SE Belmont (ground elevation street) to the south edge) so the higher volume road is closer to the majority of GPS points. Currently, if the GPS loses it’s track and then picks it back up, it looks like it would most likely to put it back on the northern most street (the lower one).
Please post here if it happens again so we can take a close look at the route.