Address Locators

[SLouq]

Are there any tutorials out there on how to build Locators? Sometimes I get spreadsheets with Address information on them and need to geocode the spreadsheet. Is there something I can use to help me with creating Locators I can use to help geocode.

[BobBooth1 · Accepted solution]

There is a tutorial in the documentation, here:

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

[SLouq]

Does it matter if the table you want to geocode is an .xlsx file or .csv file

[BobBooth1]

As long as ArcGIS Pro can read the spreadsheet (mostly about having column headings formatted right for Pro) it should work.

https://pro.arcgis.com/en/pro-app/latest/help/data/excel/work-with-excel-in-arcgis-pro.htm

https://pro.arcgis.com/en/pro-app/latest/help/data/excel/work-with-excel-in-arcgis-pro.htm#:~:text=n...

[BobBoutiette]

I have used "create locator" in ArcPro 3.4.3, making a point address locator. I have sub-addresses activated and get different search suggestion results when searching. I use the setting "give suggestions when base address is typed" and for some apartment complexes I get sub-addresses after completing the base address and others only after typing unit type and partial number. I also found it interesting that the locator did not differentiate between apt or ste. If I typed "ste", the results would still contain apt. The documentation I've referenced doesn't seem to go into great depth for locator nuances involving sub-addresses. Do you have a recommendation for more in depth material for sub-addresses locators? Thank you.

[ShanaBritt]

@BobBoutiette, it would be helpful to see the data for the problematic addresses and subaddresses to help identify the cause of the behavior you are experiencing. Or at a minimum the Reference Data Tables section of the locator properties for the locator you created for the Point Address role. Here are a few things to check:

1. Ensure that there is a feature for the base address and that it does not have any subaddress values in the subaddress element fields used to build the locator.

2. Ensure that the base address and subaddress have the same city and zip code values.

3. Ensure that the unit type and unit number are in two separate fields and have been mapped to the Unit and Unit Type locator role fields.

4. Ensure that the FeatureID role field was not mapped when building the locator,  unless you have duplicate features with different street attributes.

5. If you enable the property "Show summary of subaddresses with base address suggestion" in the locator  properties dialog, what is the suggestion that is returned for the base address where you had to include the unit type and partial unit number?

-Shana

[BillFox]

include making backup copies of the locators in your chores

locators get corrupted from time to time

[ShanaBritt]

Can you give more details about your locator becoming corrupt? Is it a locator created with the Create Locator tool in ArcGIS Pro?

[SLouq]

Thanks for the replies!