topic Address Locator not Finding Addresses in Data Management Questions

Address Locator not Finding Addresses

RachelAlbritton2 — Fri, 02 Sep 2016 16:14:02 GMT

I've created and address locator (dual range) using a reference set from our state GIS reference center. The street layer is formatted for to use for address location. My streets layer is in a file geodatabase (stand alone feature class) and my address locator is on a separate folder.

I'm using 10.4.1

To trya nd trouble shoot, I also ran through the same process to create a locator using ESRI's tutorial data for geocoding and the tutorial guide. I'm getting the same results (No Address Found).

I've read this post where a user had the same issue in 10.3.x that required a Service Pack Update to fix this issue, so I'm wondering if this, again, got overlooked when the software got upgraded to 10.4? Has anyone else had that issue. Is there something that I am overlooking?

Re: Address Locator not Finding Addresses

JoeBorgione — Fri, 02 Sep 2016 16:29:52 GMT

Check this: open up your locator properties (right click, properties). Scroll down to the Geocoding Options and expand it by single left clicking the + sign. Look at the list and make sure the Match with no zones = YES.

This ensures the locator will make a match whether or not your streets feature class has City, State, Zip etc information. I thought this was going to default to YES in v 10.4, so if it's already yes, you've got another issue going on and we can take it from there.

Re: Address Locator not Finding Addresses

RachelAlbritton2 — Fri, 02 Sep 2016 17:03:38 GMT

Thanks Joe - That got it working on the ESRI dataset and let me narrow down my problem to some fields that needed reformatting on my dataset.

Re: Address Locator not Finding Addresses

JustinConnerWR — Mon, 19 Feb 2018 17:16:44 GMT

This is still defaulting to "No" in 10.5.

Re: Address Locator not Finding Addresses

JoeBorgione — Tue, 20 Feb 2018 13:21:39 GMT

Yeah, your'e right it does. Seems like I saw a post from sbritt-esristaff‌ where she explains why ESRI stayed with that default. There may be a way to change the default locally, I'm not sure; perhaps she'll see this and let us know.

Re: Address Locator not Finding Addresses

Lake_Worth_BeachAdmin — Wed, 21 Feb 2018 19:18:40 GMT

Kind of a bummer the values are set to ='False' by default but there is a fix with arcpy to automate this process.

use the code below and set the variable "locatorPath" to the address locators ".loc" file path

do this as a last step after creating the locators.... (this is for complete automation of creating address locators, not exactly practical to use this method if your creating them manually)

filedata1 = "supportsEmptyHouseNumber = true \n"
filedata2 = "supportsOptionalZone = true"

with open(locatorPath, 'r') as file :
filedata = file.read()
# Write the file out again
with open(locatorPath, 'a') as file:
file.write('\n')
file.write(filedata1)
file.write(filedata2)
file.close()

Re: Address Locator not Finding Addresses

ShanaBritt — Thu, 22 Feb 2018 22:28:30 GMT

I wrote this technical article regarding the 'Match with no zones' geocoding option in the locator properties, which applies to ArcMap & ArcGIS Server/Enterprise 10.1+ and all versions of ArcGIS Pro. https://support.esri.com/en/technical-article/000011688 I had answered the same question in detail on the old community forums, but it is no longer accessible from what I can tell. I"ll need to poke around to see if they are backed up somewhere or not. https://community.esri.com/message/147473?commentID=147473#comment-147473

Re: Address Locator not Finding Addresses

RachelAlbritton — Thu, 05 Apr 2018 17:29:54 GMT

Shana -

I've had to create a new address locator since writing this original post and I'm still getting 100% failed results. I have read your technical article. I have set Match to No Zones to Yes, and I removed/readded to the locator from the toolbar. What can be causing this?

Re: Address Locator not Finding Addresses

ShanaBritt — Wed, 11 Apr 2018 15:28:52 GMT

Rachel:

Are you able to provide a screen shot of the locator properties (geocoding options, reference table)?

What do the input addresses look like? Are they just the street address (380 New York St) in a single field similar to the illustration in this help topic? http://pro.arcgis.com/en/pro-app/help/data/geocoding/about-geocoding-a-table-of-addresses.htm

Re: Address Locator not Finding Addresses

RachelAlbritton — Wed, 11 Apr 2018 15:58:04 GMT

Thanks for the reply Shana. Yes, my input table looks like the illustrations sent. I have included a screenshot below as well as the locator properties.

Here is a screen shot of the properties

Input Table:

I know this shows both street_address as well as the parsed address in the table. When setting up the geocoding process I am sure to choose the street address field (see below).

I'm using the same input table as last year. This year the road geometry and info are exactly the same but the schema Data Types have changed. I can use the road data set with the previous years schema and it works fine. The new schema is needed for a new 911 system being implemented. I can put together a FGDB and attach in a zip file if that would be helpful, or just let me know if I should start a ticket with ESRI?

Thank you for your time.

Re: Address Locator not Finding Addresses

Lake_Worth_BeachAdmin — Wed, 11 Apr 2018 20:12:44 GMT

try changing the option "Match without house number" to 'NO' to test.

Re: Address Locator not Finding Addresses

RachelAlbritton — Thu, 12 Apr 2018 15:16:04 GMT

Joe -

Thanks for the response. I did try that I got the same result. I did try using the World GeoService Locator Yesterday for comparison and was able to locate my address points so I may have narrowed the issue down to the new roads FC. Although it appears to be all the same data, the road segmentation and therefore the address ranged my differ in some areas causing this issue. I'll be looking at that in more detail today.

Re: Address Locator not Finding Addresses

JoeBryant1 — Fri, 20 Mar 2020 15:53:46 GMT

Hi Shana,

I'm considering pushing out "Method 2: Permanently set the 'Match with no zones' default setting to Yes/True" to my entire organization's address locator install files. We contract with lots of utilities in the US, and the address data we are supplied often does not have zip codes.

It looks like you never found your old forum post. Could you briefly explain we we wouldn't want to set the default to 'true'? There must be a compelling reason, since ESRI did not change this setting after it introduced problems way back in 10.1.

Re: Address Locator not Finding Addresses

Anonymous User — Mon, 23 Mar 2020 12:58:20 GMT

Joe I agree. They need to work on the Locators. This, plus no support for Units, different results from autocomplete vs pressing Enter etc.

Re: Address Locator not Finding Addresses

ShanaBritt — Wed, 25 Mar 2020 19:11:24 GMT

Joe:

I was able to find my response from the old thread, turns out it was moved over to the current forum system.

It sounds like you are still using ArcMap or are creating classic locators in ArcGIS Pro with the Create Address Locator tool. My response was geared to the classic locators, but the same info about creating a locator with an administrative zone (city, state, postal, neighborhood, community) applies to the new locators built with the Create Locator tool.

It is strongly recommended that administrative zones are mapped when building a locator. Region and region abbreviation are also important because they are used to help create different forms of state highways that are specific to each region or state. Not mapping them can impact geocoding quality and the performance.

Here are links to the last few explanations I provided about the 'match with no zones' property that answers why true ('yes') was never made the default:

https://community.esri.com/message/56300#comment-270455

https://community.esri.com/message/56300#comment-270458

Re: Address Locator not Finding Addresses

JoeBryant1 — Wed, 25 Mar 2020 21:03:37 GMT

Thanks Shana. I’ve decided NOT to change the default. Instead, I’ll educate our users on where to find this setting when appropriate.

Joe Bryant

GIS Coordinator

WEST YOST ASSOCIATES

direct 530.761.0226

Cell: 916-833-5840

Re: Address Locator not Finding Addresses

JeremyScott — Tue, 16 Jun 2020 13:59:26 GMT

I am having the same issue as the OP. I am trying to geolocate intersection data. I used the USA Geocoding Service in Business Analysts, but it is too broad and wasn't finding all of my intersections. I thought maybe it was a tad out of date, so I wanted to try a local roads layer to see if that would provide better results. I have created the locator from ArcCatalog but it returns no matches (including actual street addresses). When I try the Find tool, again no matches. Any suggestions why the local roads layer would not be able to match any intersections? I used the US Dual Range Addresses locator style.

Thanks

Jeremy

Re: Address Locator not Finding Addresses

JoeBorgione — Tue, 16 Jun 2020 14:12:02 GMT

The op is four years old: what version of ArcGIS are you using and how are you creating your locator? Did you make sure you toggled the Match with No Zones property as suggested? What is your procedure 'to geolocate intersection data' ?

Re: Address Locator not Finding Addresses

JeremyScott — Tue, 16 Jun 2020 14:17:03 GMT

I am using 10.7.1. I have toggled the Match with No Zones to 'YES'. I am

creating my locator from ArcCatalog. My procedure is to create the locator,

add the data to ArcMap and geocode through the normal process (File --> Add

Data --> Geocoding --> Geocode Addresses). I have geocoded for years, but

just haven't done strictly intersection geocoding. So, I'm not sure if

there are different parameters that need to be set up or not.

Re: Address Locator not Finding Addresses

JeremyScott — Tue, 16 Jun 2020 14:27:15 GMT

Joe,

Nevermind. It turns out my City fields were abbreviations and not the full

names. Once I found and fixed that, the geocod worked (albeit with quite a

few unmatched records).

Thanks for your help and sorry for the false alarm.

Jeremy