topic Re: Accessing Custom Locator Output Fields in Locator Service in ArcGIS Enterprise Questions

Accessing Custom Locator Output Fields in Locator Service

JCGuarneri — Fri, 03 May 2024 12:57:47 GMT

I'm experimenting with custom output fields in locators. The locator I create on desktop returns the field as expected. However, when I publish it as a locator service, the field is not returned (Enterprise 11.1). I don't see it as an option when configuring in experience builder, nor do I see it when I look in the rest endpoint. Is this functionality just not available? Or are there other steps I need to take?

My end goal is to be able to search for our Utility Customers by address using our custom locator, then select the related asset based on the Account.

Here it is in Pro:

And absent in the config options in Experience Builder:

Re: Accessing Custom Locator Output Fields in Locator Service

ShanaBritt — Wed, 08 May 2024 19:40:13 GMT

@JCGuarneri Are you able to show the result from the REST endpoint where you specify an asterisk for the Out Fields parameter in the findAddressCandidates form? The custom output field should be listed in that request result.

The fields listed in the Experience Builder screenshot look like the input address fields and not the candidate or output fields.

-Shana

Re: Accessing Custom Locator Output Fields in Locator Service

JCGuarneri — Wed, 08 May 2024 20:09:56 GMT

Unfortunately, I get a 400 error:

{
 "error": {
  "code": 400,
  "extendedCode": -2147467259,
  "message": "Unable to complete operation.",
  "details": [
   
  ]
 }
}

I haven't done much testing of locators from the REST endpoint, so I'm not sure if it's something I'm doing wrong or an issue with my deployment.

The trigger fields from the locator are supposed to be from the Outputs of the locator per the Experience Builder set up, but it may be using the term "output" differently than the Locator.

Re: Accessing Custom Locator Output Fields in Locator Service

ShanaBritt — Wed, 08 May 2024 20:43:25 GMT

Can you show me the REST endpoint form page that gave you the json result so that I can see what the inputs were for the parameters?

Re: Accessing Custom Locator Output Fields in Locator Service

JCGuarneri — Thu, 09 May 2024 11:07:57 GMT

Here's what I put in. I used the "POST" option.

Re: Accessing Custom Locator Output Fields in Locator Service

JCGuarneri — Thu, 09 May 2024 11:28:16 GMT

OK, so I tried Find Address Candidates instead, and that worked. It does spit out the Account field. I guess the trick is getting Experience Builder to see it.

Re: Accessing Custom Locator Output Fields in Locator Service

ShanaBritt — Thu, 09 May 2024 15:37:16 GMT

@JCGuarneri ,

There is a specific syntax you need to use for the geocodeAddresses operation via REST endpoint and you were not using it, which is why you received the error. Here is an example of the correct syntax, https://developers.arcgis.com/rest/services-reference/enterprise/geocode-addresses.htm#ESRI_SECTION1_CBF63516C84B4985A3193F1E752192AC.

The custom output fields are fields that are returned in the geocode result and not input address fields. You would not see the field listed as an input field in the batch geocoding tools in ArcGIS Pro. Based on your current Experience Builder setup from your screenshot, if you searched for a customer's address the result would include the account number. Since the account number is an attribute in the the data used to build the locator, you could build a multirole locator using the PointAddress or StreetAddress role for your existing data, then add the POI role using the existing data and just map PlaceName to the Account number field. Then when you use the locator as a service you can enter either the customer address or the account number in the 'Address or Place' field.

https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm

https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-multirole-locator.htm

https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-locator-roles.htm#ESRI_SECTION1_CE2B24E7AC144C71B645937363ECBCE5