Hi everyone, I used Create Locator in ArcGIS Pro to create a zip code locator using the ZIP role. My field mapping is just the ZIP field. I built the locator successfully. A couple questions: * In the properties for Input fields there are a ton of extra fields that I don't need (Address, Address2, Address3, Neighborhood, City, Subregion, Region, PostalExt, CountryCode). Is there a way to remove these input field options? Since this is just a zip role, all these other fields are meaningless. * When I publish this to Portal/ArcGIS Server, is there a way to limit the output fields? It is just a ZIP role yet the output fields have the full gamut of address part fields that are always going to be blank. Its a lot of clutter and confusion for users. * When looking at the GeocodeServer page of the published locator, the fields have this long list of localizednames. Is there a way to remove them entirely and/or customize which localizations show up? Thank you Josh

@Nitin_Kulkarni Are you just using the REST endpoint page to test that the service is working? What value are you passing in the Out Fields parameter in the findAddressCandidates request? Are you trying to get specific fields returned? If so, then you would specify the fields you want in a comma separated list. https://developers.arcgis.com/rest/services-reference/enterprise/find-address-candidates.htm#ESRI_SECTION1_E305B08842DB4F14A09E3E94375C1B5A In Pro 3.0 and Enterprise 11.0 we added "enabledOutputFields" so that the fields enabled in the output fields section of the locator properties are only returned in geocode results in client applications. This enhancement fixes the problem described in post you referenced above, Limit Geocoding Information Returned by Locate Tool in the Locate pane and in the Show Details pop-up. The "enabledOutputFields" property listed on the service description page for geocode services published to Enterprise 11.0 or later is not used in REST requests. If the service was added to Pro, the fields in the "enabledOutputFields" list would be returned for the results in the Locate pane.

Hi @ShanaBritt We are using geocode operations via the REST endpoint page. Thank you for confirming that the geocode service's description page is not tied to Output fields section in ArcGIS Pro.

@Nitin_Kulkarni Can you provide more details on how you are using the service? Are you using the geocoding operations via the REST endpoint pages or are you using the service in a web app or ArcGIS Pro? The Address and Candidates fields section of the geocode service's service description page are not tied to the Output fields section listed below in the Locator Properties dialog in ArcGIS Pro. The Candidate fields represents all of the possible fields that can be returned by the locator in the geocode result.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create Locator Zip role excess fields

joshkalovcook

Hi everyone,

I used Create Locator in ArcGIS Pro to create a zip code locator using the ZIP role. My field mapping is just the ZIP field. I built the locator successfully. A couple questions:

In the properties for Input fields there are a ton of extra fields that I don't need (Address, Address2, Address3, Neighborhood, City, Subregion, Region, PostalExt, CountryCode). Is there a way to remove these input field options? Since this is just a zip role, all these other fields are meaningless.
When I publish this to Portal/ArcGIS Server, is there a way to limit the output fields? It is just a ZIP role yet the output fields have the full gamut of address part fields that are always going to be blank. Its a lot of clutter and confusion for users.
When looking at the GeocodeServer page of the published locator, the fields have this long list of localizednames. Is there a way to remove them entirely and/or customize which localizations show up?

Thank you

Josh

Find more posts tagged with

Accepted answers

All comments

Nitin_Kulkarni

@ShanaBritt

Yes, that is correct, I am referring to the Address Fields and Candidate Fields section on the description page.

If we cannot limit the output fields on the descriptions page, where/how do we get limited fields view when geocoding addresses that we have set in Locator Properties > Output fields?

I understand, we cannot see the limited fields (or enabled fields) in the Locate Tool, according to the answer on a similar question here - Limit Geocoding Information Returned by Locate Tool

Our end goal is to display only a few fields in the geocoding result to improve end user experience.

Shana Britt

@Nitin_Kulkarni ,

Are you referring to the Address Fields section and the Candidate Fields section of the geocode service description page?

Nitin_Kulkarni

Hi @ShanaBritt ,

We are using ArcGIS Pro 3.0.5 (as we cannot upgrade to 3.3 yet) and ArcGIS Enterprise 10.9.1. Created a composite locator using Create Locator tool, checked only a few required fields (for example: Address, City, Region, Postal, Country) under Locator Properties > Output fields, published the locator as a geocode service, still we see all fields at the REST endpoint for the GeocodeServer.

Could you recommend any other way to limit the number of output fields for the geocode service?

Thank you!

Nitin.

Shana Britt

Josh:

1. The input fields are fixed for all locators created with the Create Locator tool regardless of the role the locator is based on. If it is just zip code, you should be able to use the SingleLine input field. Is the purpose of using the geocode service at the REST endpoint for development purposes to verify results or will the geocode service be used in an application?

2. To limit the output fields returned by the locator, turn off the unwanted fields in the Locator Properties of the locator in ArcGIS Pro on the Output fields page of the dialog. Then overwrite the service using the modified locator.

3. It's not possible to remove or customize the localized names for the locators created with the Create Locator or Create Feature Locator tools that are published as services.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.