Upon trying to navigate to the cemetery, Waze ended navigation on the road running along the northern edge of the cemetery. So, I tried this myself using the live map and navigation seems fine. It takes you to the entrance defined by the entry point of the cemetery as expected.
However, when I tried it in the app on my phone, there does appear to be some kind of issue with both the primary route and the alternative.
So I’m wondering if anyone can shed any light on why the app is trying to send you through a hedge, despite the entry point working on the live map.
Thanks in advance,
Craig
Screenshot from reporter:(unavailable attachment: ss1.png)
On searching - appeared to be that the Google location was not linked, hence two entries appearing in the search.
The search results with a “coloured in” marker, are ones that come directly from Waze, whereas the other type are results from Google.
I’ve linked the two, and as search results update essentially Live (not linked to Tile updates), if you try it again it, they both now go the the entrance
I did wonder if it was to do with the lack of a linked place, as I noticed the two results that came up on the live map.
Although on the live map, both options still gave the correct navigation instructions and endpoint, but not on the app. I’ll put that down to Waze weirdness
One thing to note when dealing with URs like this, is that when using Android Auto (and maybe CarPlay, I don’t know), sometimes voice search results (e.g. OK Google, navigate to Redstone Cemetery) use the Google result and ignore the Waze place, regardless of whether its linked or not.
