World Geocoding service REST reverse geocode's returnIntersection

AutoReturnAutoReturn — Thu, 08 Jan 2015 19:04:58 GMT

The World Geocoding service REST interface for reverse geocoding has a parameter named "returnIntersection". When set to "true" it is supposed to cause the service to return the closest intersection instead of the closest address. It does not appear to do anything.

The requests

http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer/reverseGeocode?f=json&location=-120.6976456245268,38.2048532311486&returnIntersection=true

and

http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer/reverseGeocode?f=json&location=-120.6976456245268,38.…

return the same thing, even though the point listed is on an intersection and quite far away from the address that gets returned.

Am I missing something or is it just broken?

Re: World Geocoding service REST reverse geocode's returnIntersection

BradNiemand — Fri, 16 Jan 2015 18:24:20 GMT

There is an issue with the returnIntersection parameter getting ignored. We will address this with the next release of the online service.

Brad

topic World Geocoding service REST reverse geocode's returnIntersection in ArcGIS REST APIs and Services Questions

World Geocoding service REST reverse geocode's returnIntersection

Re: World Geocoding service REST reverse geocode's returnIntersection