There is a section on I-70 Westbound, just before Rostraver Road that looks normal on the map, but when you drive it, Waze suddenly shows your car sliding sideways (like if you drive down a street that Waze thinks is one-way on the opposite direction).
If starts happening approximately mid way between the 2 exits shown on the map (the very middle of the screen), just after the bend, and stops about 50 yards before the exit ramp on the left of the screen. There is no junction at that point in the road, so I am a bit baffled as to the cause.
I can only guess that maybe the satellite image that the waze map is traced over isn’t lining up with the actual roadway, so maybe it thinks you are momentarily driving on the wrong side of the freeway?
I have driven the route many times, and it always happens, but every time I look at the map, I can’t tell why. HELP. Note: That section of I-70 is locked.
I noticed this as well, as I travel that road once and a while. I thought it was a bug with Waze on my phone, not a mapping issue. Since you experienced it as well, something must be up. I can unlock it and take a stab at fixing it, but I don’t want to step on any toes. I will toss mapcat a PM and ask him to chime in as he was last to edit. Is there a lane shift here with construction or is that further down toward Washington that I am thinking about?
I wouldn’t think so. There is only a low hill to the north of the freeway. It doesn’t display the GPS signal lost message. I have had it happen on 3 different phones (LG Optimus, Droid Incredible, and Droid Bionic). It happens every time, not just occasionally.
One would think that Waze would apply some logic and make an educated assumption that a vehicle is generally going to continue in the same direction it was heading, on the same road (especially if there was no abrupt change in speed).
I see someone yesterday reported wrong driving directions because Waze thought they were in the eastbound lanes.
Different issue, but same general area…
Can someone please fix the locked westbound ramp shown by the map issue here so that Waze does not try to route you onto the wrong ramp.
That ramp on the left side of SR-51 should be blocked if you are travelling north on SR-51. That should then cause Waze to route to the correct ramp. https://www.waze.com/editor/?zoom=4&lat=40.15594&lon=-79.77564&layers=BFTFTTTFTTFTTTTTTTTTFT
Exactly why I think it’s poor GPS reception in that area. Happens every time on multiple devices. The SmartPhones may not update the GPS reception data instantly on the display. If the GPS is only lost for a few seconds you would not even know.
There are several places on my regular commute where GPS reception is lost for a couple of seconds and the results are the same in regards to my Waze route and GPS tracks in the editor.
What is really odd is that when I look at my recent drive traces, it shows me on the correct side of the road (Westbound). Almost perfectly tracing right over the road, until just before the Rostraver Rd ramp, at which point it shows me on the Eastbound side.
The point where it shows me on the wrong side of the road is actually AFTER the point at which Waze goes back to normal.
I looked at the street view on Google Maps to see what the terrain is like. There is a clear view of the sky West, East, and South. North has a grove of trees along the side of the road, and you can still see sky through the trees, so no mountain behind. I don’t see why there would be any problem getting a good GPS fix there. Phones are mounted on a windshield mount.
I know I’m VERY late to this conversation, but I used to have a similar issue on Delaware Route 1. On different sections northbound & southbound, there were stretches of the roadway where I would be lost on the phone client. GPS tracks matched and there was no rhyme or reason for why this would happen. I ended up disconnecting both ends of the roadway so they were floating loose, saving my work, then reconnecting. Of course I also made sure the turn restrictions were correct after reattachment.
After the next map update, the issue was resolved. Still not sure why it happened, but maybe you can apply this methodology for that stretch to see if you have any results? It couldn’t hurt.
