Someone reported that the system took them to a spot on the backside of the block for the perkins rest. they were going to.
https://www.waze.com/editor/?zoom=5&lat=44.85197&lon=-93.28832&layers=1989&env=usa
I checked the street address of the location and the street number on the map editor and they match and are correct. Any thoughts?
Waze routes to the closest segment so if it is even 1m off and closer to the other segment in waze, this could happen. I’m mobile so can’t check the UR or address.
The marker in Google and the house number in Waze for Perkins at 8324 Lyndale are physically closer to Aldrich Ave behind the parking lot. Move the marker in Google and the house number in Waze so that they are physically closer to Lyndale, and the GPS coordinates that Waze uses should then keep the wazer on Lyndale. Follow the guidelines for setting the stop point in the correct location. Worst case, if that fails (it shouldn’t) and reports are still being generated, map a parking lot road into the lot, which allows Waze to route closer to the coordinates.
If you haven’t seen this portion of the FAQ, it has more detail about address lookups.
This is about 0.25 miles from my airport bubble area at MSP. Otherwise, I could help out a bit.
