Could we maybe get a new locator that does default to no zones? I just have no reason to use them as my addresses are only with my city and don't cross county or state lines. I do use Left/Right City though. Also the zones, does this only work for Zip codes? Could we just use the Left/Right City as the zone by mapping the zipcode fields to these?
There are no plans to change this default setting, as this is by design. The default design of the locator is to not return match results when you build the locator without zones and do not include zones with the input address because of the performance cost when having to search through the entire index of the reference data to return multiple candidates, which would take longer to do. Of the multiple candidates returned, there may be many that are correct. You wouldn't know which is the correct candidate to be matched if you didn't have a zone. The performance hit would be really significant for larger geographies, but I know a lot of customers create local locators for their city or county and create them without referencing a zone cause it's all the same. But, just about every city has a Main St�?� how do you know which Main St is correct if the county has multiple cities and they all have a Main St? Or like in Chicago, IL, the street Lake Shore Drive spans 15 different zip codes.The article "Dual Ranges address locators created with ArcGIS for Desktop 10.1 do not return matches" provides a more permanent solution that modifies the USAddress locator template to make 'Yes' the default setting so you don�??t have the change the properties of every locator after you create it.The match with no zone setting was also discussed in the Geocoding -Advanced Techniques technical workshop at the 2012 International User Conference, which can be viewed in the demo between time frame 20:49 - 20:06. The corresponding slides for the time frame in the demo can be found at http://proceedings.esri.com/library/userconf/proc12/tech-workshops/tw_2022.pdf starting at Managing Performance.I hope the above information helps and if it does not, please submit a request to Technical Support.-Shana
I have SP-1 with 10.1 and I still have the problem with address locators and having to tweak the Geocoding options. Will there be a fix?Thanksjj
A standard practice that I have seen when it comes to geocoding addresses at the local level is to create an address locator that does not include zonal attributes (city, state, zip, emergency service number, community name.... are not mapped in the field mapping) and just find or geocode a list of addresses with just the house number and street name. The reason that the locators created without zone field mappings based on the Dual Range locator style at 10.1 do not find any matches is because the default setting for the 'supportsOptionalZone' property in the rules is set to false/no. This property determines whether or not addresses will be found or matched if a zone is not included in the input address in the geocoding toolbar, find tool, or batch geocoding. To enable the supportsOptionalZone property of an existing address locator created at 10.1 use the following steps. Setting this option to "yes" will affect the performance for larger geographies. 1. In ArcCatalog or the Catalog window, right-click the address locator 2. Click Propertiesâ?¦ 3. In the Geocoding Options section change 'Match with no zones' from â??noâ?� to â??yesâ?� Locator performance properties -Shana B
This IS NOT fixing my basic dual range geocoder that works in 10... Big Bummer. I guess I better alert my co-workers!
To enable the supportsOptionalZone property of an existing address locator created at 10.1 use the following steps. Setting this option to "yes" will affect the performance for larger geographies. 1. In ArcCatalog or the Catalog window, right-click the address locator 2. Click Propertiesâ?¦ 3. In the Geocoding Options section change 'Match with no zones' from â??noâ?� to â??yesâ?� -Shana B
A standard practice that I have seen when it comes to geocoding addresses at the local level is to create an address locator that does not include zonal attributes (city, state, zip, emergency service number, community name.... are not mapped in the field mapping) and just find or geocode a list of addresses with just the house number and street name. The reason that the locators created without zone field mappings based on the Dual Range locator style at 10.1 do not find any matches is because the default setting for the 'supportsOptionalZone' property in the rules is set to false/no. This property determines whether or not addresses will be found or matched if a zone is not included in the input address in the geocoding toolbar, find tool, or batch geocoding. To enable the supportsOptionalZone property of an existing address locator created at 10.1 use the following steps. Setting this option to "yes" will affect the performance for larger geographies. 1. In ArcCatalog or the Catalog window, right-click the address locator 2. Click Propertiesâ?¦ 3. In the Geocoding Options section change 'Match with no zones' from â??noâ?� to â??yesâ?� [ATTACH=CONFIG]17330[/ATTACH] Locator performance properties -Shana B
Experiencing same kind of problem using a composite locator built of 4 custom address locators. Everything is working fine and we are getting results with ArcGIS 10.In ArcGIS 10.1 the locators are building without any errors, but only 1 of 4 locators returns results. No results returning for the rest 3 locators.
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
