Hi
Had this UR raised for Glebe Rd in Bedford:
When selecting Glebe Rd, Bedford in the app, the user is incorrectly routed to Glebe Rd in Ampthill
Permalink
I’m guessing this is probably some issue with Google, as using the "More results for glebe road’ option in the app and selecting Glebe Rd, Bedford, Bedford routes correctly
If you search in google maps for ‘Glebe Road Bedford’ it it incorrectly drops the pin on Glebe Rd Ampthill.
How can I fix this? Thanks
In both the browser and Android app versions of GMaps here, searching for “Glebe Road Bedford” gives me a choice of two results - one in Bedford and the other in Ampthill. Viewing the debug console whilst searching for the same keywords in Livemap shows that the GMaps API returns the same two results here as well, with the Ampthill one listed first…
Although the order in which the GMaps API returns results doesn’t seem to matter - if you search for “High Street High Wycombe” in the Waze app, the second result claims to be for the High Street in High Wycombe, but selecting it instead takes you to the High Street in Lane End, which is the 4th result returned by the GMaps API.
So the problem just seems to be that the app doesn’t handle GMaps API responses all that well when there’s more than one suggestion with an exact match for the street name, plus a match for any other keywords entered.
Thanks
Is there anything we can do you fix this or is it just an unfortunate ‘feature’?
Not that I can think of - the GMaps API always tries to offer up alternatives, so it’s really up to the Waze app to interpret the returned data in the most appropriate manner.
What I have noticed here is that, when you search for Glebe Road Bedford, the first result is listed as being x miles away, where x miles is the correct distance for the actual Glebe Road in Bedford, so it does seem as if the app initially gets it right, but when you then tap on the result to start the route calculation process, it switches over to using the Ampthill result instead.
Any chance you could pop a response on the UR regarding this? Just a bit wary of replying, trying to give a reason and not providing correct information. Would appreciate it 
Hmm, too late… Seems one of our L5’s has decided to try fixing the problem by deleting the old Glebe Road segment and creating a new one in the same place. Not entirely sure how effective this’ll be given what the cause of the problem actually seems to be, but I suppose there’s a small chance that regenerating the segment in the Waze map data might somehow alter how the servers then process the corresponding search data from Google.