Reverse Geocode returns the wrong city

[ewagstaff]

Hi, I'm using the REST API's /reverseGeocode endpoint to find admin boundaries after users submit points. However, the accuracy of the results in one case makes me concerned about the accuracy of the system as a whole. For example, this query for 3011 Linden Street in Oakland returns that the point is in Emeryville, the neighboring city. A Google search shows that the point is in Oakland, several blocks from the Emeryville border.

I'm concerned that this inaccuracy may be more prevalent than just this case, since it's wrong in a heavily urbanized area where the admin boundaries should be easy to check against. Does anyone know about accuracy issues with this geocoder and what can be done to correct them?

[ShanaBritt · Accepted solution]

You may want to consider using the preferredLabelValue in your request, which will return the expected city you are looking for (preferredLabelValues=localCity). According to the USPS zip code lookup the zip code 94608 is recognized as both Emeryville and Oakland. More details about the preferredLableValue with examples can be found in the following help topic https://developers.arcgis.com/rest/geocode/api-reference/geocoding-reverse-geocode.htm and examples https://developersdev.arcgis.com/rest/geocode/api-reference/geocoding-reverse-geocode.htm#ESRI_SECTI.... Here is the request for the address mentioned in your original post: https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer/reverseGeocode?f=json&location=-...

[ewagstaff]

Wow, I cannot thank you enough for pointing this out. That does appear to clear things up.