As part of Esri’s commitment to delivering cutting-edge solutions in the geospatial domain, we are excited to announce a series of enhancements to our geocoding service.
Our latest update includes bug fixes, quality improvements, and additional functionalities that not only improve your experience but also provide more accurate and reliable results.
Quality Improvements
Our team has been diligently addressing bugs and implementing numerous quality improvements to enhance your interactions with our services.
In addition to those improvements, the team has added some new functionality to the API and service output:
- A new type of search, and corresponding Addr_type value, is supported by findAddresscandidates and geocodeAddresses — StreetBetween. It allows you to search for a street between two intersecting cross streets, such as “Conway Dr between Sheridan Ave and E El Norte Pkwy”. Street Between is the category value that can be used with the category parameter to limit search results to StreetBetween candidates.
- The outFields parameter is now supported for reverseGeocode requests. It allows you to specify a smaller set of output fields to be returned in the JSON response.
- A new API parameter, returnInputLocation, is now supported for reverseGeocoderequests. It allows you to display the location of the input X/Y coordinates which were submitted in a reverseGeocode request as a point on a map.
Requirements:
To access the ArcGIS Geocoding service, you will need an ArcGIS Developer account or an ArcGIS Online account, along with an access token (API key or OAuth 2.0).
Learn More about World Geocoding Service
Ready to get started with our World Geocoding Service? Click the link below to learn more:
Additional Help:
For more information on our data coverage, please visit the ArcGIS Geocoding service Data Coverage page. If you have any additional questions or need software support, please contact our dedicated support team.
For detailed information on the improvements made in this update, visit the What’s New page.
Article Discussion: