topic Re: Geocoding sub-addresses in Geoprocessing Questions

Geocoding sub-addresses

Darrin-Smith — Wed, 09 Feb 2022 14:57:36 GMT

ArcGIS Pro 2.9 Map tab-->Locate Tool-->Search

The issue is the Locator will not return results for an address with sub units (e.g. 123 Main Street Apt 1). It only returns one choice for the primary address. I have created a geocoding locator as a PointAddress Role and input all parsed fields including Unit, Building, Level in addition to Prefix, Name, Type, etc.

According to Primary locator roles, or Tips for improving geocoding quality, for field mapping, I can either reference a Unit field or I can reference the same Unit field for From/To where both the values are the same.

I have also enabled sub-address suggestions in my Locator properties Suggestions for partial subaddresses.

Here is what I expect the results to be where in this example they actually use a keyword Unit, but I don't believe that is even necessary. Using type ahead, 3700 Dean Dr. should return all the choices.

Re: Geocoding sub-addresses

Michael_Knapp — Thu, 03 Aug 2023 20:26:34 GMT

Did you ever find resolution to this? We're also having issues with subaddresses not being suggested.... we're using Pro 3.1

Re: Geocoding sub-addresses

Darrin-Smith — Thu, 03 Aug 2023 21:27:01 GMT

Yes our locator is now performing as expected. Here are things I either learned from esri tech support or learned through trial and error:

For the Create Locator tool:

if you have buildings, use the BUILDING input not the BUILDING NAME input

specify a POINT ADDRESS role if you have points that represent the location
if you want better return for the type of unit, e.g. Unit, Suite, Apartment, populate a field to store those values and reference that field in the row for UNIT TYPE
After your locator is created, examine the Locator Properties under Geocoding Options. Make sure all the boxes are checked for Subaddress. Also for type ahead performance, I use “Suggest as partial unit is typed”

For interactive Locate within Pro or through a webmap, (https://nconemap.maps.arcgis.com/apps/instant/media/index.html?appid=c51b8ef4c4334835807a2850b7daa855) add on a number in your type ahead to retrieve sub units (for example at type “215 n pine 1” to return many returns where the unit number begins with 1
For interactive Locate within Pro, make sure “Show All Candidates” is checked
If you have sub addresses but no parent, the sub address won’t be found. You must create a parent. For example, if I have a point “100 MAIN STREET UNIT 1”, but there are no points for “100 MAIN STREET”, Unit 1 won’t be found.

Re: Geocoding sub-addresses

Michael_Knapp — Thu, 10 Aug 2023 22:56:15 GMT

If you have sub addresses but no parent, the sub address won’t be found. You must create a parent. For example, if I have a point “100 MAIN STREET UNIT 1”, but there are no points for “100 MAIN STREET”, Unit 1 won’t be found.

Thanks Darrin........ not having a parent address was our issue. We scripted those to be added and the subaddress portion of the locator works perfectly now.

Re: Geocoding sub-addresses

AdamCottrell — Wed, 06 Mar 2024 20:01:19 GMT

Would you care to share the script to that you used to add points based off of subaddesses? I'm running into the same issue. I'm currently in the process of moving our LGIM data into Pro and I'm finding a lot of nuances that seem to break years of work done in ArcMap.

Re: Geocoding sub-addresses

Darrin-Smith — Thu, 07 Mar 2024 13:56:45 GMT

Attached zip contains a readme and a python script.

Assumes you're running within Visual Studio Code and not Pro. It uses many pathname variables you would need to define.
The premise of the script is:
- Export a selected set of your addresses that contain sub addresses e.g. 100 MAIN ST UNIT 1
- Use a cursor to mimic ADDJOIN that determines if a parent exists in the primary set e.g. does 100 MAIN ST exists and if not create a new faux point.
- Create a mean center faux point based on the cluster of the sub addresses that don't have a parent.
- Append the faux set and the original set to create a complete set that can be used as input to CREATE LOCATOR

Re: Geocoding sub-addresses

AdamCottrell — Thu, 07 Mar 2024 14:21:44 GMT

@Darrin-Smith Thank you!

Re: Geocoding sub-addresses

AdamCottrell — Thu, 07 Mar 2024 19:44:05 GMT

I'm having issues with the Global and boto3 modules. The "ProgressBar" too but I'm less worried about that at the moment. See errors below. Running Python version 3.9.18. I will try to do more research on it this evening try again tomorrow. Thanks for the assistance. I'm fairly new to python.

Re: Geocoding sub-addresses

Darrin-Smith — Thu, 07 Mar 2024 22:36:08 GMT

Keep in mind, this code is just one part of thousands of lines to accomplish many specific tasks. The imports at the top of the script are just residual for my purposes. I would say you can delete all those lines except for import arcpy and possibly import datetime as time is reported through the script. If you look at the INPUTS/OUTPUTS near the top, I tried to give you an idea of variables used in the script. I retain all my variables in Global hence the import statement you are having issues with. You will need to define your local variables and my recommendation would be to use the ones I have to do so. For example, the variable for "in_layer_name_path" should point to your featureclass for all your address points. You'll also find I use fields you might not have and schema's I use that might not be applicable. At a minimum, to resolve geocoding issues with sub addresses, you need to create a faux point that has a parent and append that point to your master set and then run the Create Locator on that set in order to account for the parent. My script will tell which points don't have parents. Then your geocode result should give you options for the parent sub addresses. My script goes one step further to actually determine where the mean center of the faux point should be based on proximity to all the sub addresses. Hope this helps.

Re: Geocoding sub-addresses

AdamCottrell — Thu, 07 Mar 2024 22:42:30 GMT

Thanks. I made the changes to the input/outputs. I really appreciate the notes! I was confused with the imports mostly. So that explains it.

Again, thank you so much. I appreciate your assistance and response. I should be able to get this off the ground shortly. ...As long as I'm not pulled in another direction before then. 😕

Re: Geocoding sub-addresses

amarcz_cc — Thu, 11 Apr 2024 23:54:07 GMT

Any recommendations when you have a main address and subaddresses, but the Geocoder wont find it until you type it in perfectly?

IE: Input Type = Single Field

Input Address: 31750 Landau Blvd 3A Cathedral City CA 92234

Only finds if I adjust the '3A' to 'A3' and then it finds its?

Do I have to remove the 'Unit Type' in the Locator?

Or maybe I need to spend more time breaking up the address to multi fields?

Re: Geocoding sub-addresses

Darrin-Smith — Tue, 16 Apr 2024 12:13:56 GMT

Did you look at the Suggest options in the Locator properties?