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

Address Locator Spelling

JoshBillings

Hello all,

I have a published Gazetteer Locator that my org is using for citizens to pay fees. When citizens search for their address in the application sometimes they will put "North" instead of "N" or "Street" instead of "St." Our address point layer used by the locator uses abbreviated suffixes and street types. The address locator is bringing back these addresses as invalid.

Is there a way to increase the tolerance as to what the locator will allow? Will the spelling sensitivity property assist with this or is there another property that I can manipulate in order to fix this?

Any help is appreciated - Thanks!

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

JoshBillings

@ShanaBritt My apologies, you're right it was created with the Create Address Locator tool.

I built a locator using the Create Locator tool using the Point Address role. This locator works great in Pro! When published to Server, it doesn't seem to be able to find address candidates. Could this be due to the lack of functionality present in 10.6?

Shana Britt

@JoshBillings Based on the product versions you mentioned, it sounds like you used the Create Address Locator tool to build the locator in ArcMap 10.6 or ArcGIS Pro 2.6 or earlier. The Create Locator tool is only available in ArcGIS Pro and does not have a spelling sensitivity property to adjust. Are you able to provide a screenshot of the locator properties to confirm the version of the locator? You could use an alternate name table to account for the prefix direction and street type abbreviations when building the locator.

If you have ArcGIS Pro available to you, you can build a locator with the Create Locator tool using the point address data you have with the the PointAddress locator role, then publish the locator to Enterprise 10.6 and use the service in ArcMap, but you wouldn't have all of the new locator functionality in this version of Enterprise.

JoshBillings

Thanks for the reply @ShanaBritt.

The Create Locator tool was used to build this locator originally.

We are using ArcMap and Enterprise v10.6 for this locator.

Users do not need city or zip code but the option is available.

Shana Britt

@JoshBillings

What tool was used to build the locator?

What version of Pro was used to build the locator?

What version of Enterprise did you publish the locator to?

Will users enter the address with or without the city or zip code?

Have you attempted to create the locator with the Create Locator tool to see if you get better results?

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

-Shana

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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