#Google maps api update#
We plan to roll out an update to the Geocoding API at the end of November 2016 that will increase the difference between Geocoding and Places performance for ambiguous and unambiguous queries. Place search is also more robust at responding to queries with additional non-address information such as business names or apartment numbers.
Place Search is better at coping with ambiguous queries than the Geocoding API, and lets you restrict your search to a specified area, or rank results by distance, allowing more precise filtering and ranking of results for ambiguous or incomplete queries. What if you have an application that handles ambiguous or incomplete queries in an automated fashion, with no user able to provide input?įor geocoding ambiguous or incomplete addresses in automated systems, when there is no user to select one of the autocomplete suggestions, we recommend the Place Search service in Places API. The Place Autocomplete service relies on a user to choose the best option from multiple results. Results can also be biased to prefer those near the area shown on the map or near the current user location Typing '123 Main St' into a Place Autocomplete search box lets the user choose from multiple results. It’s also good at handling misspelled queries, or queries containing non-address information, since as the user types, they can see suggestions and correct their spelling if needed. Since the Place Autocomplete service is optimized for responding to user input, it also has very low latency, usually at least 10x lower than the Geocoding API. The autocomplete lookup function can also be biased to return results specific to a location, enabling high quality results to be returned for incomplete queries such as “123 Main St”. This service is designed to return multiple possible addresses and allow the user to choose between them.
Place Autocomplete serviceFor applications that respond in real time to user input, we recommend using the Place Autocomplete service in the Places API. If your application handles user interaction, or addresses that are ambiguous or incomplete, consider the following services. In contrast to the Geocoding API, it handles ambiguous or incomplete requests in a more robust way. Geocoding API is best used for unambiguous complete addresses, such as '48 Pirrama Rd, Pyrmont, NSW, Australia' Places APIThe Places API allows users to discover both addresses and semantic locations, such as cafes or parks, by name or type. However, Geocoding API is not recommended if your application handles ambiguous or incomplete queries, such as “123 Main St”, or if it handles queries that may contain non-address information such as apartment numbers or business names. Compared to other Google APIs, the Geocoding API provides the best quality matching of addresses globally for these types of complete, unambiguous queries. The Geocoding API is best for handling unambiguous queries: complete postal address strings (for example, “48 Pirrama Rd, Pyrmont, NSW, Australia”). Note that while this blog focuses on the server-side Places and Geocoding APIs, these best practices also apply to the client-side Places and Geocoding services in the Google Maps JavaScript API. What are the differences between them and when should you use each one? Here’s where to start. The Google Maps APIs have several services that you can use to convert addresses into coordinates - the Geocoding API, the Place Autocomplete service in Places API, and the Place Search service in Places API. Forward Geocoding is the process of converting addresses (like a street address) into geographic coordinates (latitude and longitude), which you can use to place markers on a map or position the map.
0 kommentar(er)
