Address locator "skips" over a known address

[Danielle_Journey]

I have an address locator built from a feature class that contains all of our address points down to the suite level.  The address locator works perfectly for finding the suite addresses in a building, but will not find the main building address.  For example, it will find 412 VILLAGE DR 200, but will not find 412 VILLAGE DR.

I've tried the follow with no luck:

• Checked all the fields in this address's record to look from spelling errors, trailing spaces, etc.  
• Rebuilt and recreated the address locator several times, even tried adding a duplicate address point "from scratch" before building the address locator.  
• The new address locators have been built inside and outside of a file geodatabase.  
• I exported out the address point feature class and built an address locator on the new feature class
• Rebooted & crossed my fingers.

Has anyone had this happen?  I am completely stumped as to what else to try..  

I'm using 10.3.1 with the locator style attached.

[MichaelVolz]

Go into the Properties of the Address Locator and open the Geocoding options section.

Towards the bottom of this section (at least for me) is the setting Match with no zones.

Just change Match with no zones to Yes

[Danielle_Journey]

I tried that, and with a small sample of data, I get zero matches.  When setting up the US Address - Single House Subaddress Locator Style, which fields did you pick from your reference data?  

I used only my address points feature class as a primary reference table with these fields

[MichaelVolz · Accepted solution]

I would try using SubAddr Unit instead of Building Unit as that is how I have it configured and working as shown in a previous post.  I would also try not using City or Place, ZIP Code, or State as those are also blank for me and the address locator is providing me with what appears to be good results.

[Danielle_Journey]

Michael - worked beautifully!  Thank you very much!!!

[MichaelVolz]

Danielle:

Is it your expectation that endusers of your address locator would be putting in address information that would include City, Zip Code, and/or State?  If so, you might want to test out your results if entering that additional information as it could change the match score and thus not return the results you are expecting.

But I am glad you've got it working!!!

I also personally think that Match with no zones should be set to Yes by default instead of No (But that is just my opinion based on my personal experience). 

[JoeBorgione]

I also personally think that Match with no zones should be set to Yes by default instead of No (But that is just my opinion based on my personal experience). 

I thought I heard at sometime that was going to happen, but I guess not at least in 10.3.1.....

[ShanaBritt]

The "Match with no Zones" setting was originally default to 'Yes' at 10.0, but since 10.1 it's been 'No' as the default. It affects performance for large areas (Regions, Nationwide), not so much for small areas like city or county.

[ShanaBritt]

If you are able to upgrade to 10.5 or higher, there is only one pair of Subaddress elements for field mapping when building a locator with the US Single House Subaddress style.