Hi all We have a store locator on our website which seems to be working perfectly. Users enter their postcode or suburb and state, we geocode that and then compare it to all the stores in our database that have a stored lat/long.
I have recently discovered a problem whereby postcodes often don't return the correct stores. It looks to me like this is due to the Australian postcode data in Google Maps being inaccurate. Has anyone else found this, and have you been able to overcome it in any store locator applications? As an example, searching for "Cheltenham, VIC" on http://www.google.com.au/maps works correctly by pinpointing the correct location on the map (the middle of the suburb name). However if you enter Cheltenham's postcode "3192" instead, the pin drops onto a location that is apparently 8km away from Cheltenham. This results in the Cheltenham store not being shown to users. This is the same behaviour we are experiencing in our store locator - searching for "Cheltenham, VIC" works as expected, but searching for "3192" shows us stores 7-10km away. Has anyone else noticed this and developed a work-around? Or is there some way we can bring inaccurate postcodes to the attention of Google so they can be fixed? thanks Josh -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
