| Bug ID Number |
BUG-000135146 |
| Submitted | November 4, 2020 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS Pro |
| Version found | 2.6.2 |
| Operating System | Windows OS |
| Operating System Version | 10.0 |
| Status | Non-Reproducible
This issue was not reproducible when tested by the development team. Issues may be given this status when they cannot be reproduced or are no longer relevant in a development version of the software, but a specific fix was not installed to address the issue. The issue's Additional Information section may contain further explanation.
|
Additional Information
The behavior is not reproducible when the locator is created with the Create Locator tool and the PointAddress role when the Precision Type optional parameter is set to 'Local Extra High' or 'Global Extra High'. If a multirole locator is created with the Create Locator tool which includes the PointAddress role, select one of the Extra High Precision Type options to get match results that are closer to the location of the primary point reference data.
For an explanation of the Precision Type options see the precision_type parameter in the Create Locator tool help topic, https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/create-locator.htm.
Workaround
There is an alternate parameter named precision that can be set in the Create Locator tool in ArcGIS Pro 2.6 to give more accuracy to the search address. Set to Global Extra High or Local Extra High to give a location, which closer to the original geometry location.
Steps to Reproduce