Hi,
I’ve just responded to a UR which is a result of the usual Google Maps random address placing. :roll:
I’ve fixed it with street numbers, however, the street in question is “A161 - Marsh Ln”. As most people wouldn’t bother with the A161, it then still defaults to the wrong end of the street. One possible solution would be to add “Marsh Ln” as an alternate name for the segment in question. However, I’ve just checked the 'pedia and (understandably), this isn’t covered.
I’m just wondering if this would be a legitimate solution to get around (a) our naming convention and (b) Google’s randomness. Thought I’d check first before doing it!
Cheers,
Dave
I think in this case it is easier to suggest an edit to Google for 59 Marsh Lane. 57, 61, 63 all locate correctly, in Google and hence the App. I’m still not convinced the App priorities our own data over Google. It doesn’t matter what we name our segments the dynamic search results (as you type) give Google data. You have to tap Search and then it might list our own data.
That’s an even better idea, thank you! I’m glad I asked. 
I’ve just suggested the change, lets see how long they take to respond… if they even respond at all! I’ve pretty much given up suggesting corrections to the GM as they always ignore them, even when you copy a SV link in as evidence. :roll:
I definitely agree that the Waze data appears to have a lower priority than Google data. It does make you wonder how much point there is in entering places and numbers onto the map if it’s going to be ignored over Google. Discussion topic? 
Dave