BUG-000094346 for ArcGIS for Server

Bug ID Number	BUG-000094346
Submitted	February 23, 2016
Last Modified	June 5, 2024
Applies to	ArcGIS for Server
Version found	10.3.1
Operating System	Windows OS
Operating System Version	7.0 64 Bit
Status	Known Limit

Additional Information

This limitation is explained in the "Suggest limitation" section of the ArcGIS REST API: Work Geocoding Service page on the Suggest operation: https://developers.arcgis.com/rest/geocode/api-reference/geocoding-suggest.htm#ESRI_SECTION1_F4600031F2F44E44ACE0989325BC9E0D The issue has been addressed and rolled out to the ArcGIS World Geocoding Service and for new locators that ship with Street Map Premium this month. However, this fix has not yet been rolled out for users who create locators based on their own data. This is being worked on for a future release of ArcGIS Desktop. Previously, for performance reasons, the house number (or unit number in the case of US Address - Single House Subaddress style) is not used in the suggestions capability. The implications of this are that while house numbers are displayed in generated suggestions, they are not validated until a geocoding request is sent. Therefore, if the house number typed by users does not exist, it is displayed in suggestions but are not returned from the geocoding results. A best practice when creating a custom locator using suggestions is to create a composite locator with at least a street address or point address locator and a Street Name locator. Doing so ensures that if the house number does not exist in the Street Address or Point Address locator, there is a fallback match to the Street Name.

Workaround

Create a locator in ArcGIS Pro 2.3+ using the Create Locator tool and publish the locator in ArcGIS Pro using Share Locator to a federated portal, or using Python, or using a publisher or admin ArcGIS Server Connection file created in ArcMap/ArcCatalog, or publisher connection file using ArcGIS Pro 2.3.

https://pro.arcgis.com/en/pro-app/help/projects/connect-to-a-gis-server.htm#GUID-E3F3174D-3895-4BFC-9443-8676D2D4964B and the sample in the CreateGeocodeSDDraft https://pro.arcgis.com/en/pro-app/arcpy/functions/creategeocodesddraft.htm