Problems with Google Geocoding handling of new developments

jamezpolley commented 6 years ago

In cases where there's a new development, with planned new streets that don't yet exist, our current Geocoding implementation often gives results that aren't useful.

As an example, https://www.planningalerts.org.au/applications/1055843 - the address that's being used here seems to be the Apple store in Rundle Mall.

A better location would have been to match on the suburb of Virginia:

https://www.google.com.au/maps/place/Virginia+SA+5120/@-34.6699155,138.5333328,13z

Front conversations

Updating this description to include a list of test addresses:

[ ] 1 Wickham Street Marsden Park NSW 2765
- Google puts this in Newcastle instead of Marsden Park
[ ] 7 Bradfield Street Flagstone QLD 4280
- Google puts this somewhere else in brisbane. Mappify/OSM can't find the address at all.
[ ] 21 Beck Street Park Ridge QLD 4125
- Google puts this at 21 Beck St Paddington :/
[ ] 8 Bennelong Cres Lloyd NSW 2650
- Google puts this in 2614 (Macquarie ACT) instead of 2650
[ ] 16 Hilltop Gr, Cliftleigh 2321 NSW
- Google puts this in 2430
[ ] 17 Isabella Close, Narara NSW 2250
[ ] 41 Foxall Street Riverstone NSW 2765
[ ] 29 Larkin Street Marsden Park NSW 2765

andrewharvey commented 6 years ago

Hah that's interesting, Google Maps fails to find that address, but it is in GNAF http://results.openaddresses.io/sources/au/countrywide and other Geocoding API providers which use GNAF should be able to locate it.

google