This used to work ok but a recent complaint shows users are being given a destination to the POI instead of the navigation point. I tweaked it a few days ago to force a refresh but still no good after recent map update.
Destination: Tesco Extra, River Way, Andover. The POI is correctly mapped and linked to the google location. Instead of getting a route to the front of the store (navigation point), users are being asked to stop on the dual carriageway behind it (nearest segment). The destination appears to be the google location instead of our navigation point.
Hi David
I would guess that the long section of PLR to get to the marker is causing a large penalty and Waze is calculating that the stop on the main road is quicker. The google point is fine, I don’t think that is an issue and the points are linked in the Waze place.
If Waze had the ability to have entry 2 points, you could have one at each entrance to the road running around the place, but that is not here (yet?). Putting it at one end would just confuse half the drivers. It may help if you moved the marker out onto this section of road, rather than close to the building. There would be less PLR to get to the marker, therefore less penalty.
Looking at the road running around the Tesco, I personally would probably change both ends of that that to a street, leaving the middle (about a third) as a PLR. (Currently I would guess it is a private road, not a PLR, but that will not help). This will then give you a good place to put the marker.
Keeping the middle section as a PLR should stop Waze routing through here, but I would guess the locals are already doing this.
Anyway, that is my thoughts on it, you may want to see if anyone else has a better idea before implementing anything.
Cheers
Definitely looks like a google place issue. Navigating on the waze place navigates correctly to the car park, but navigating using the google place stops on the dual carriageway. I’ve had similar issues to this in the past at my local sainsburys whereby there was a bus stop with the same name as the store. Renaming the bus stop in google maps by just adding ‘bus stop’ to the end of it fixed that. Could you have something similar going on here? Maybe not a bus stop, but an additional google place that isn’t linked to the waze place?
It could be a cached version of the destination, nothing shows as a phantom location in my App, routes fine. Delete all instances of this destination and search again.
I see it routes wrong on LiveMap. Always use your App to check, never trust LiveMap.
Thanks all for your thoughts. This does appear to be related to the google location. I see that the google POI has been slightly moved - now to the front of the store. Searching in both app and livemap using a fresh search (not history) now routes correctly - result! I haven’t made any changes.
I believe there may have been an issue with Waze’s search server sending the wrong coordinates to the routing servers, making the navigation point attach to a street and not the PLR. Not sure there’s anything we can do about this.
Waze is searching for the closest segment with the same name as the address on the place, and sending the coordinates for that rather than the navigation point.
It did this to be going to the Tesco Petrol Station in Warrington as shown here: https://imgur.com/aKCq6p9
the address of this petrol station is Winwick Road. So it’s sending the driver to Winwick Road, rather than the PLR leading into the petrol station.
It may help if you moved the marker out onto this section of road, rather than close to the building. There would be less PLR to get to the marker, therefore less penalty.