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; } } }

Geocoder requires City to find a match

PhilLarkin1

When using geocoders on 10.7 (Point Address, Street Address) I'm unable to find a match if the City field is not populated. When used in ArcGIS Pro 2.4, the city field is not required and I get good returns.

Has anyone else noticed this issue?

Shana Britt‌

Trouver plus de publications taguées avec

Accepted answers

PhilLarkin1

Well, the answer back from Support is one that has been given since at least 10.1:

Modify the loc file to include: supportsOptionalZone = true

Manually editing a file is kludgy. I'd really like to see:

Locator properties exposed in arcpy
Locator properties exposed in the UI for Create Locator and Create Address Locator tools in ArcMap/Pro.
Snickers bars mailed out to all the users that test new products extensively and version after version ask for the same enhancements/bug fixes.

Thanks for your help Eric and Joe.

All comments

JoeBorgione

Phil- I had a really great virtual visit with Shana Britt‌ during the UC and we discussed the upcoming improvements to geocoding in 2.6. I'm looking forward them!

PhilLarkin1

Arcpy at Pro 2.6 now includes a Geocoding module and Locator class.

Locator—ArcGIS Pro | Documentation

PhilLarkin1

Apparently this has been fixed in 2.5. I have not tested.

ENH-000124557 [Enhancement] Provide the ability to set the "supportsOptionalZone" property for a locator built with the Create Locator tool in ArcGIS Pro directly from the UI

https://my.esri.com/#/support/bugs/ENH-000124557

PhilLarkin1

Well, the answer back from Support is one that has been given since at least 10.1:

Modify the loc file to include: supportsOptionalZone = true

Manually editing a file is kludgy. I'd really like to see:

Locator properties exposed in arcpy
Locator properties exposed in the UI for Create Locator and Create Address Locator tools in ArcMap/Pro.
Snickers bars mailed out to all the users that test new products extensively and version after version ask for the same enhancements/bug fixes.

Thanks for your help Eric and Joe.

JoeBorgione

Eric: you better get some snickers bars stocked up....

EricAnderson17

Hi Phil,

To expand on my previous message, looking at more information about the "location" parameter (documentation is for the World Gecoding Service, but the principles are the same), I see this following note:

The location parameter can be used in place of administrative zone (city) or postal code in an address search, as long as a matching address exists within 50 kilometers of the input location. Consider the following example.
251 Vesey St, New York, 10282 is an address in Manhattan, New York City.
Coordinates -74.006,40.71437 represent a point within central Manhattan, less than one kilometer away from the address.
If you search for "251 Vesey St"(no city or postal) with location=-74.006,40.71437included in the request, a match to 251 Vesey St, New York, 10282 is returned. However, if instead you search for"251 Vesey St" with a location value in Washington, DC (350 kilometers away) an address match is not returned.

findAddressCandidates—ArcGIS REST API: World Geocoding Service | ArcGIS for Developers

So because ArcGIS Pro is including this location parameter, the city name is not required. Therefore, this may be expected behavior but it may be good to still log that Support case so we can confirm fully and document this for future users who may have this same question/issue.

Best regards,

Eric

EricAnderson17

Got it, thank you for the clarification Phil! I'm seeing the same thing on my end with a Point Address locator I created in Pro 2.4 and published to Enterprise 10.7.1.

What's odd is if you bring that geocode service into ArcGIS Pro (Catalog pane > Portal tab), it behaves the same way as the local locator and allows you to search for the address without a city. So it seems like only when submitting a request directly from the REST end-point of the service is the city name required.

From what I can tell from Fiddler, the difference is that the request from ArcGIS Pro includes a "location" parameter, while the request from REST does not (unless of course you specifically include one). If I take the "location" parameter and simply include that onto the REST request, it is successful.

I'd say we have enough here to investigate this a little more thoroughly and I would definitely recommend following up with that Support case. If you want to reference this GeoNet post, I'd be happy to link up with the analyst who takes ownership and pass on my testing notes.

Best regards,

Eric

PhilLarkin1

Hi Eric, thanks for your reply.

I am publishing to ArcGIS Enterprise 10.7 via ArcGIS Pro 2.4. When searching via the geocode service, specifically findAddressCandidates, City appears to be required. When testing the locator that is published to Enterprise in Pro, the desired behavior is experienced: locator returns results when City is not passed.

findAddressCandidates 10.3.1 and 10.7

EricAnderson17

Hi Phil,

Can you expand on what you mean by "When using geocoders on 10.7". Are you using ArcGIS Desktop 10.7? ArcGIS Enterprise 10.7?

You stated you used the Create Locator tool in ArcGIS Pro 2.4 and when used in ArcGIS Pro 2.4 you "get good returns". So where exactly are you seeing the issue with no matches being returned without a city? Can you provide any relevant screenshots?

Thank you,

Eric

PhilLarkin1

I suppose removing City from the logic is a reasonable workaround for a small set of addresses. However, I'm trying to serve 200k addresses in various jurisdictions with matching street names. I want my locator to distinguish between cities, but I don't want this to be a required entry.

Thanks again for your input.

JoeBorgione

I've been fighting with.... errrr I mean I've been using the Create Locator tool in 2.4 for the past few weeks and find it to be challenging. (Trying to be nice here....). The match out of range thing is a mystery to me. Mine have worked without passing a city, but when I create the locator, I only field map those fields I want, so I don't check anything I that is 'zone' related. No Neighborhood, No Metro Area, No City and so forth.

Here is a copy of the parameters I use in an address point role:

Parameters
Country or Region USA
Primary Table(s) AddressPoints PointAddress
Field Mapping
'PointAddress.HOUSE_NUMBER AddressPoints.ADDR_HN';
'PointAddress.STREET_PREFIX_DIR AddressPoints.ADDR_PD';
'PointAddress.STREET_NAME AddressPoints.ADDR_SN';
'PointAddress.STREET_SUFFIX_TYPE AddressPoints.ADDR_ST';
'PointAddress.STREET_SUFFIX_DIR AddressPoints.ADDR_SD';

You can capture this info when the tool completes: I use it so I can script creating locators.

Calling Eric Anderson‌ ; are you there?

PhilLarkin1

Hi Joe, thanks for your reply.

I am using the Create Locator tool in ArcGIS Pro 2.4. I had tested 'Match out of range' set to Yes and No with no positive result. I'd expect a user to be able to pass a simple address, without sending a city.

JoeBorgione

Did you use ArcGIS 10.7 and the create address locator tool to create your locators? If so, you need to go to the locator properties, Geocoding Options and change 'Match with no zones' from NO (the default) to YES.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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