Routing Issue

Hi,

There are now several URs for routing to 8888 216st. I can’t see any issues with turn restrictions in the area. I have checked pin placement in waze and google, there are no duplicates and the pin is placed correctly. It appears that waze does not want to route to the location, even though it works in Live Map. Is it due to the fact that the pin is on a Private Road? I thought waze will still route to locations on private roads… Is this a bug or some other issue?

Some thoughts on why this may be happening would be appreciated.

https://www.waze.com/editor/?lon=-122.86151&lat=49.21375&zoom=6&layers=997&segments=74482898&env=usa

Thanks,
Kayos

Hi,

I have tested this location through LiveMap and driving there myself with my client from four difference locations. In each case, Waze had correct directions, but for three of the driving tests it did not direct me onto the private road, only to the entry intersection.

I have not heard back from the URs in this area as to whether this is a consistent or intermittent issue, or what client versions are being used.

Kayos

Is the private road a dead-end?

No, it’s a single road into the housing complex and there are several internal roads, so theoretically waze would be able to loop through the private installation and back out again. There is one segment which is a dead end though which is set correctly and is not near the location pin. The roads follow the private installations wiki and I can’t see anything wrong with other roads and turn restrictions in the area.

Thanks,
Kayos

This is continuing to be an issue for routing.

Street numbering for 8888 216st has been added to the waze map. For now I’ve left the google pin location in place.

Thanks
Kayos

Have you refreshed your map cache?

If it still has problems, please open a thread in the Routing forum…

New thread opened in the Navigation and Routing forum:

https://www.waze.com/forum/viewtopic.php?f=6&t=101078

Kayos