Reverse Geocode Returns No Subaddress

595
8
Jump to solution
09-29-2021 12:42 PM
MattFancher1
New Contributor III

Hi All. I created a locator in Pro 2.8.3 and published it as a geocode service to ArcGIS Server 10.7.1. The locator includes the Point Address and Street Address roles. I cannot get the REST reverse geocode operation to return a subaddress result. I submit an x/y I know is on an address point with subaddress info (i.e. unit type and number) but instead of returning that record it returns an address point farther away that does not have any subaddress info associated with it.

Anyone know if this is expected behavior? Or do I have a configuration problem?

Thanks in advance!

 

0 Kudos
1 Solution

Accepted Solutions
ShanaBritt
Esri Regular Contributor

@MattFancher1 This is expected behavior for ArcGIS Server 10.7.1, support for reverse subaddress matches was not supported until 10.9. The local version of the locator will return the expected results in Pro 2.8.x using the Reverse Geocode tool and interactive reverse when using What's here?. The following help topics will reflect the additional functionality that is supported once the next ArcGIS Pro and ArcGIS Enterprise versions are released later this year.

- https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/publish-a-geocode-service.htm

https://pro.arcgis.com/en/pro-app/2.8/help/sharing/overview/share-a-locator.htm#GUID-0E990A85-7CA9-4...

https://developers.arcgis.com/rest/services-reference/enterprise/reverse-geocode.htm

 

View solution in original post

8 Replies
JoeBorgione
MVP Esteemed Contributor

I suspect this is expected behavior with the configuration you mention.  Check this post:

https://community.esri.com/t5/arcgis-pro-questions/help-leveraging-unit-and-building-address-element...

Where new geocoding functionality with respect to unit number suggestions is discussed with pro 2.9 and Server 10.9.1.

@ShanaBritt might be able to clarify.

 

That should just about do it....
MattFancher1
New Contributor III

@JoeBorgione Thanks for your reply.

I read the post you suggested, and I'm looking forward to the upcoming enhancements related to subaddress suggestions and searches described by @ShanaBritt. But here I'm talking about the REST reverse geocode operation and its ability to return subaddress results. It's not working for me. For example, here I'm using findAddressCandidates to return an address point with subaddress info:

https://gisweb.columbus.gov/arctest/rest/services/Locators/OneViewComposite/GeocodeServer/findAddres...

If I take the X/Y coordinates from that response and feed them back into the reverseGeocode operation of the same geocode service, I'd expect to get the same address point back as the top result. But I don't. The reverse geocode operation returns an address point result that is actually farther away than the one I want:

https://gisweb.columbus.gov/arctest/rest/services/Locators/OneViewComposite/GeocodeServer/reverseGeo...

I've experimented with the featureTypes property in my request, but no luck with that so far.

 

 

0 Kudos
JoeBorgione
MVP Esteemed Contributor

Oh.  REST end reverse geocoding?  That's a horse of different color for sure.  All I can say is good luck with it!

That should just about do it....
0 Kudos
ShanaBritt
Esri Regular Contributor

@MattFancher1 This is expected behavior for ArcGIS Server 10.7.1, support for reverse subaddress matches was not supported until 10.9. The local version of the locator will return the expected results in Pro 2.8.x using the Reverse Geocode tool and interactive reverse when using What's here?. The following help topics will reflect the additional functionality that is supported once the next ArcGIS Pro and ArcGIS Enterprise versions are released later this year.

- https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/publish-a-geocode-service.htm

https://pro.arcgis.com/en/pro-app/2.8/help/sharing/overview/share-a-locator.htm#GUID-0E990A85-7CA9-4...

https://developers.arcgis.com/rest/services-reference/enterprise/reverse-geocode.htm

 

MattFancher1
New Contributor III

Thank you @ShanaBritt. It's good to hear that functionality is coming soon

0 Kudos
CityofColumbusDepartmentofTech
New Contributor

Hi @ShanaBritt. I created a geocode service using Enterprise 10.9.1 and was happy to see the reverse geocode enhancement for subaddresses working like you described. One follow up question though. Is there a way to get the unit number to appear in the "address" attribute of the reverse geocode response?

Here is an example reverse geocode request. If you look at that you'll see the address attribute doesn't show the unit number, but other attributes such as the match_addr do. I'm unfortunately working with a vendor whose COTS solution uses the "addresss" attribute so I'd love to figure out a way to get it in there. Thanks in advance for any advice.

 

 

0 Kudos
ShanaBritt
Esri Regular Contributor

@CityofColumbusDepartmentofTech , unfortunately there is no setting to return the UnitName or SubAdr fields that show up in findAddressCanddates requests in reverseGeocode requests or to have it included in the 'Address' output field. From a reference data security standpoint, someone could use reverseGeocode requests to reverse engineer your reference data.

One workaround to consider involves some data manipulation, but you could use Calculate Field to populate the 'Address' field in the geocode result with the value from the Match_addr or LongLabel field.

Out of curiosity, what is COTS?

You could submit an idea for this or an enhancement through TechSupport.

0 Kudos
CityofColumbusDepartmentofTech
New Contributor

Thank you @ShanaBritt  for the reply. I greatly appreciated your participation in this forum and your expertise.

COTS is "Commercial Off The Shelf". It applies to software that you buy and use without customization. In my case it's a web application than integrates with an Esri geocode service. It allows a user to place a pin on a map and then populates a form with information from a reverse geocode json response at the pin x/y. For better or worse, it is coded to use the "address" attribute from the geocode service response to populate the "address line 1" field in the form. The vendor considers using any other attribute from the json response a customization, which of course means more $$.

I may submit an idea or request an enhancement as you suggest. In my opinion the unit number should definitely be included in "address" attribute for a subaddress feature type. 

0 Kudos