The UR on the roundabout complains that when navigating to the Nissan Car Dealer (bottom left) waze wants to stop on the flyover.
Stu connected a road to the ramp and a waze place was created and linked to the google location.
Waze correctly identifies the destination but will not navigate to it via the ramp and new road. Waze still wants to stop on the flyover.
It looks as if the new road is not shown on the livemap, even though tile updates were made since.
If you’d previously tested the navigation here in your app prior to Stu’s fix, then you’ll need to make sure any reference to the destination has been deleted from your app destination history before you attempt a fresh routing request, otherwise your app will continue to use the old position for the destination rather than the corrected one.
The new road will also probably not show up in your copy of the app until you force a refresh of the map data in that area, as right now it’ll be using the cached tile data from last time you viewed this area.
I’ve had a good look at this. There are some issues that I can see, but I’m pretty sure what the problem is.
First off - the Livemap. You’re right, in that the access road for Nissan isn’t showing on there. The
Livemap being out of date visually is not unusual. It often happens that the display tiles fall behind. Normally, in this situation, you can ask for a route on the Livemap and you will see the route using the invisible new segments. But in this case, Livemap routes to the flyover, suggesting the routing tiles haven’t updated either. I’ve added a few more access roads in the immediate vicinity in the hope of triggering a tile update.
Then I checked the app - and things got confusing. The app shows that Nissan access road and routes correctly to the correct location when I search for West Way Nissan. As far as I know, that’s impossible - the app & the livemap get their routes from the same place.
So I went back to the Livemap. My failed routing to the flyover was based on a destination search for “West Way Nissan”. I set a destination point fractionally to the right of the flag - as close as I could - and Livemap routed to the correct location via the correct access road! So Livemap routing seems to be exceptionally and strangely sensitive to the precise location of the stop point. I’ve slightly extended the access road to the left to see if we can improve that.
Anyway, after all that, back to your user. As my test in the app showed, routing to West Way Nissan works correctly in the app. The most likely reason they are having a problem is a historical search entry in the app. When you navigate to a destination, the app stores that entry in it’s history - including the precise lat/lon returned when you did that search. Every time you navigate to that historical search entry the same position is used, regardless of any future updates to the map.
If you get the user to delete the entry from their history and search for West Way Nissan afresh, that should resolve their problem.
I don’t think that’s always true - there have been a few occasions where I’ve been working a UR and seeing different results between livemap/route checker results and what my copy of the app is returning at the same time. Don’t know why it was happening though…