Geocoding: Match out of range

98
4
11-18-2019 07:33 AM
Highlighted
MVP Esteemed Contributor

ArcGIS Pro 2.4.0

What is the logic of the 'Match out of Range' setting in a locator created with the create locator tool?  By default it is set to Yes.

I geocoded a table of addresses against a multi-role locator that has Address Points and Street Address roles. When I rematch, there are no candidates found. However, with the same locator active in my map, I can get get a 98.9 score on an address that does not exist with the Locate tool:

Eric Anderson

Tags (1)
Reply
0 Kudos
4 Replies
Highlighted
Occasional Contributor

Hi Joe,

The "Match out of Range" option allows you to still get a successful match even if the address is out of the designated house number range but still falls within a reasonable threshold. 

Tips for improving geocoding quality—ArcGIS Pro | ArcGIS Desktop 

This would most likely require a little investigation. I tested this out on my end and can confirm that a house number which falls out of range is successfully returned as a candidate from both the Locate pane and Rematch Addresses pane. 

Have you tested this with other addresses within the same locator? What about with a different locator all together? 

Best regards,

Eric

Reply
0 Kudos
Highlighted
MVP Esteemed Contributor

I just don't see the point inn matching an address that the data does not support. But from our other thread, it sounds like I can suppress that...

Reply
0 Kudos
Highlighted
Occasional Contributor

Right, the documentation I sent above makes a pretty good use case - "This will ensure that you don't miss a potential match because the data isn't 100 percent up to date." However, if you are good about keeping your reference data up to date, then keeping the "Match out of range" option set to False/No should continue to work well for you. 

Reply
0 Kudos
Highlighted
MVP Esteemed Contributor

Ah-ha!  Happy to say that  I'm spoiled with very good data to work with!

Reply
0 Kudos