Has anything changed on geocode API

Question

I just wanted to know if anything changed on geocode API from 21 st February because before 21st it was validating zip code 9 digits but from yesterday it is giving an error on 9 digits zip code and now it only validating 5 digits zip code.

Answer 1

More information in your question would be helpful.

I haven't noticed any change, but I thought I'd take a look at the GeoCoder Documentation FAQ for you.

Yes, based on that date, I'd say something changed recently.

Perhaps this is what you're referring to, but that's only a speculation since you didn't provide any detail or examples.

Troubleshooting

I’m getting more queries that return ZERO_RESULTS with the new geocoder. What’s going on? In the new geocoder, ambiguous, incomplete and badly formatted queries, such as misspelled or nonexistent addresses, are prone to produce ZERO_RESULTS. These queries would typically produce incorrect results in the old geocoder, such as returning the suburb if the address could not be found. We believe that returning ZERO_RESULTS is actually a more correct response in such situations.

If your application deals with user input of addresses, the Place Autocomplete feature in the Places API may produce better quality results. Place Autocomplete allows users to select from a set of results based on what they’ve typed, which allows users to choose between similarly named results, and to adjust their query if they misspell an address.

If you have an application dealing with ambiguous or incomplete queries or queries that may contain errors, we recommend you use the Place Autocomplete feature in the Places API rather than the forward geocoder available in the Geocoding API. For more details, see Best Practices When Geocoding Addresses and the Address Geocoding in the Google Maps APIs blog post.

---

More Information:

• Documentation FAQ

• Related Issue Tracker