Can anyone see anything I’m missing on this UR, which might be causing the reporter to be abandoned on the A34 beside the golf course, rather than being taken to the correct entry point, on the road that runs perpendicular underneath? I’ve had a handful of matching URs for this place over recent years and, each time, have jiggled the entry point, added alternative names etc, but it seems to keep happening.
I tested on my phone and Waze directs me correctly. I guessed possibly the user used postcode to search the destination but postcode will not direct us to A34. Another possibility is to ask the user to clear the history/cache or refresh the map. The last thing we can do is to delete to place and remap it.
If you plan the drive on Waze.com (live Map) you will end on A34, probably because it is still using a coordinate address for the centre of the Golf Course area rendering. Nearest navigable segment is on the dual carriageway.
I am learning to always check that the arrival flag is at a reasonably sensible place before ‘Save to App’, having had a similar problem on one of my own journeys.
They will now need to delete any faulty journeys/searches to get sent to the correct destination marker.
Hope this makes sense and helps.
I had this exact same situation personally when driving to Styrrup Golf Club in Nottinghamshire (link). End of route was on the A1 :x. Almost missed my tee time! I worked it out to be linking from my iPhone calendar which uses Apple Maps for the location field. I tested that here though and it seems to be ok now but it could be that the user did the same a long time ago before it was fixed and they’re just running off cached searches.
I have had 4 UR’s in the last few days with the same issue. The entry point is fine, but they are being directed to the closest road to the place. I suspect we have a bug on the loose.