Geocoding Results Spatially Off

[DavidBuehler]

I created a locator in Pro using the "Create Address Locator" geoprocessing tool.  It was a "US Address - Single House Subaddress". Then I ran the "Geocode Addresses" geogprocessing tool against a table of addresses, using the preferred location type of address location, and checked the categories.

What I am seeing is the geocoder has matched all of addresses in the table with almost 100% certainty.  However spatially the results are off from the actual point.  The results are any where from .3' to a foot and half off.

I have checked the data from the source and the map are in the same projection.

I am a loss.  Should they not line up exactly?

[JoeBorgione]

The results are any where from .3' to a foot and half off.

Given the season, my first thought is you have a lot to be thankful for...  

I guess in theory they should be, but that level of precision would be more than good enough for me...

[DavidBuehler · Accepted solution]

It is just odd that it should line up with an existing feature, but it does not.  Nothing to lose sleep over, so I am moving on.

[ChipBrownHBG]

David:

This happens with our locators as well. Did you ever find an explanation?

[MariaGiarrusso]

Hi. Having similar issue.  Using the Pro 3.3 modelbuilder Geocode Addresses tool, I get results that are off by up to 100 ft or more.  If I use the ArcGIS Pro 3.3 Locate tool, the first result is correct, but geocoding using the same locator and addresses gives a different result.  Unfortunaly this case doesn't allow my results to be good enough.  Has anyone found a solution?  Thanks in advance.

[ChipBrownHBG]

No.  No one ever responded to my question. Still very curious about it though.

[MariaGiarrusso]

I opened a case w/ ESRI (#03661884).  I was able to change the settings of the locator to get the desired results.   Here are some notes from my case. Hopefully this is helpful for you too. 

• Original issue:  The geocoded points do not fall over the reference data and has an offset ranging from 0.5 feet to 1.5 feet to in ArcGIS Pro.
• Created a new locator using the "Create Locator tool" with the following parameters:
• Country or Region: United States
• Primary Table(s): E911Address_Points_Current_Cranston; Role: Point Address
• Field Mapping: House Number: Address_Number; Street Name: Street_Name; Suffix Type: Street_Type_Suffix; Full Street Name: Full_StreetName; State: State
• Optional parameters: Precision Type- Local Extra High.
• The default precision type "Global High" has a precision of approximately 0.5 meter, which is consistent globally. Hence, we were getting an offset in the Geocoded result.  Instead use  Precision Type- Local Extra High.
• Match with no Zones = 'Yes' and comprehensive zone matching = ‘No’ in the Geocoding options
• Geocoded the "LocatorTest_E911PtsTable" with the newly created Point Locator, and the output feature layer did not have any offset and was lying on top of the original points.