Yet another example of Google data being used over the correctly mapped Waze data I've linked the Google data to the Waze data and our own location should now override the incorrect info. You may need to delete this from your recent history for the app to use the new data.
 

MrSoapsud wrote: ↑Tue Jan 18, 2022 4:03 pm ...I've removed the link to the one in the field which should help Waze behave. If you wish you can report the wrong location to Google in the hope they remove it. 
As for the spelling, I'm not sure I get your point? Apparently it's called Powis Castle even though it's in what now generally referred to as Powys!
Regards
Martin
P.S. Chris - we should only link to the SY21 8RF locations





 

No, this is the total opposite of correcting the error. By removing the wrongly located Google means when selected in the Waze results users will be taken to the wrong location. By linking the wrong Google location to the correct location in Waze users who select the wrongly placed Google result in Waze will have their selection use the Waze data instead. We can not stop bad Google locations being shown as results in Waze searches. This is the whole point of linking Google locations to Waze locations.
 
 
 Feel free to request Google remove their bad data but we can't rely on them bothering so we must ensure any Google result selected in the Waze app directs to the correctly mapped Waze location.
 

This is local(ish) to me. The "Powis" spelling is an Anglicised (and/or historical, depending on your point of view!) version of the Welsh name - Castell Powys.

Many thanks for fixing this! Re. the spelling, I just wanted to highlight that both spellings produce the same result, wasn't sure if it was relevant. Thanks again.

Hi again,
I think this is a similar problem to your other request in that it's the overlap with Google Maps that's the problem. On there someone's added an erroneous Powis Castle location in the middle of a field! However, the Waze "Powis Castle" location has been linked to both the correct and wrong locations in Google maps. I've removed the link to the one in the field which should help Waze behave. If you wish you can report the wrong location to Google in the hope they remove it. 
As for the spelling, I'm not sure I get your point? Apparently it's called Powis Castle even though it's in what now generally referred to as Powys!
Regards
Martin
P.S. Chris - we should only link to the SY21 8RF locations

gareth71 wrote: ↑Tue Jan 18, 2022 6:55 pm This is local(ish) to me. The "Powis" spelling is an Anglicised (and/or historical, depending on your point of view!) version of the Welsh name - Castell Powys.

 

I thought that would be the case but the NT sign visible on Streetview calls it "Castell a Gardd Powis"! You would think they'd done their homework? Probably just as well it comes up with either spelling...
Martin
 

atrophicshiner wrote: ↑Wed Jan 19, 2022 4:42 pm No, this is the total opposite of correcting the error. By removing the wrongly located Google means when selected in the Waze results users will be taken to the wrong location. By linking the wrong Google location to the correct location in Waze users who select the wrongly placed Google result in Waze will have their selection use the Waze data instead. We can not stop bad Google locations being shown as results in Waze searches. This is the whole point of linking Google locations to Waze locations.

Sorry Chris - brain fade! We were both editing at the same time and what you've just reminded me of here is exactly what I did for Loz's other request! I can't understand why I got this so wrong.
Must have been having a bad day...
Sorry again
Martin