How to change server rest parameters for Geocoding Service?

[Yogesh_Chavan]

Hi all,

We have an ArcGIS enterprise 10.9.1 standalone server deployment with Geocoding service published through ArcMap, its a composite locator.

We have built all locators from ArcGIS Pro now, and going to proceed with Publishing the composite.

Before we publish, can someone advice/suggest how are the rest parameters determined for Geocoding service request at the server REST?

When we created the composite from ArcMap we see fields shown as in REST as well:

But when creating composite we see a different set of field mappings, and we already have a test on 11.4 which shows REST as shown below:

The only question is if we publish a composite geolocator built from ArcGIS Pro to 10.9.1, will it retain the same parameters as Street, city, zip, and country OR will it follow Address, Address2, Address3..., and if Yes, can this be controlled to show Street, City, Zip and Country?

cc @ShanaBritt Tagging you for your helpful advice 🙂

[ShanaBritt]

Short answer is if you publish a composite that contains locators created with the Create Locator from Pro to 10.9.1 you will get all of the input fields and you would not be able to change this. If you attempted to remove the unwanted fields in the composite, the locator wouldn't work as expected.

The locators created in Pro with the Create Locator tool will always have the Address, Address2, Address3... input address fields, which will carry over to the composite locator because the participating locators have all of the input address fields. So if you publish the composite the contains locators created in  Pro with the Create Locator tool, you will get the input fields Address, Address2, Address3... when published to 10.9.1 or 11.4. You would see the same fields if you published one of the participating locators created with the Create Locator tool to 10.9.1 or 11.4.

The locators created in ArcMap or with the Create Address Locator tool have different input fields that will show up in the composite locator. Those locators have fewer input fields that would show in the composite locator. So when the composite is published to 10.9.1, there are fewer input fields you would see on the REST endpoint page.