nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Different addresses are geocoded to one point

Anonymous User

I recently uploaded a list of addresses and ran into several issues. As you can see in the below pictures one particular point has 7 data points mapped at that one location. However, the 7 data points represent 6 different addresses. I looked but couldn't find a particular thread or help section that addressed this. Thanks for your help.

Geocoding issues 1.JPG

Geocoding issues 2.JPG

Encuentra más publicaciones etiquetadas con

Accepted answers

ChrisWhitmore

Hi Matthew - when you uploaded the file, there was a dialog that listed the fields inside the file. The dialog should have also displayed which fields will be used for geocoding. Typically, this relationship is obvious (City -> City) and easily deduced but sometimes an address field isn't easily interpreted. Looks like that may have happened in your case, judging from the fields in your screenshot. The 'Addr1' field didn't correctly map to Address level matching in the geocoder, which explains why the seven addresses were all centered in the City (which was correctly matched).

You can fix this be re-adding the file and selecting the Addr1 field to be the Address location field, as shown below.

To fix:

All comments

StevenGraf1

Did you use Esri's World Geocoder? I'm guessing that it couldn't find the street addresses for those 7 points so it defaulted to the City. Are all those points in the center of Shippensburg, PA?

-Steven

Anonymous User

How can I tell if I used Esri's World Geocoder? I went to Add Layer, selected from file, and chose the file with the addresses. It does appear that they all defaulted to the center of Shippensburg PA. Any suggestions for how to remedy this? Check out the picture below. Point A is where the 7 points were mapped. Using's ArcGIS Online's directions feature I searched for the address of one of points that's mapped at Point A. It correctly finds the address, which is Point B below. If it can find it in the search feature why wouldn't it geocode correctly?

StevenGraf1

Strange that the directions would find the correct address while the geocoder didn't. It appears you are logged into ArcGIS Online, correct?

To see what geocoder you are using in ArcGIS Online, go to your portal and login, Click My Organization, Edit Settings, Utility Services.

To remedy it, it would be best to build your own locator service but you would also need ArcGIS Server to publish it. I'm not sure if you can upload an address locator to ArcGIS Online or not. It doesn't seem to give me an option to load a local geocoder.

Anonymous User

Thanks for your help. I am using the Esri World Geocoder. I'm not too familiar with ArcGIS so I'm not sure how I'd go about building my own locator service. I work for a non-profit and we received the ArcGIS Desktop software so I imagine that ArcGIS Server is included in that package.

MikeVolz

I would doubt that you would have received ArcGIS for Server software as that is much more expensive software and is designed to build web-based services.

StevenGraf1

What you could do is create the point file on your desktop version of the software and upload that information to be used on ArcGIS Online.

-Steven

JeffWard

How widespread are your addresses? Are they localized to a single city or county? You could ask them if they could geocode your addresses for you. The locators they have would be way more accurate than Esri's world locator.

ChrisWhitmore

You can fix this be re-adding the file and selecting the Addr1 field to be the Address location field, as shown below.

To fix:

Anonymous User

Thanks for the suggestion. I'll have to look into that.

Anonymous User

In total it will be over 800 points across 27 counties. And I'll need to update the mapped points every so often.

Anonymous User

Thank you Chris. That was the issue. In an attempt to redeem myself a little I'll explain how I messed that up. When I originally uploaded the file, as you said, the Addr1 field was not linked to address. So I changed it to Address. After making that change I noticed that the "Region" (not in your screen shot) was "World" and not "United States". I then changed it to "United States" and while I thought it would save the Addr1 -> Address pairing it did not. So it defaulted to the city only. When you originally posted your response I didn't think that would be the solution as I remembered selecting Address. Thanks for your help. While the map now is much more accurate I'm a little disconcerted that other users suggest using a different geocoder as the Esri World Geocoder may not be the best option. Is that something I should be concerned about? I plan to spot check the map I just created but I don't want to have to validate all of the points.

Thank you everyone!

ChrisWhitmore

Great, good to hear! Makes sense on what happened with the Addr1 field resetting to unmatched. When switching regions, the fields revert to the default matching as outlined above. This happens for basically the same reason - different regions have different address matching fields (province, district, locality) so it's difficult to make assumptions when switching regions if the field name is not a fairly explicit match.

As for the Esri World Geocoder vs a custom geocoder - the Esri world geocoder typically has high accuracy (at least when I've used it and seen reported). What others may be referring to is that sometimes the address field matching may not sync up with your data, resulting in less accuracy (as you've experienced). This has sometimes happened with zipcode fields containing hyphens, for example. With a custom geocoder, you have control of the configuration options for the geocoder and can tailor it to match your data (for instance, if you have high precision addresses like apartment numbers you could potentially match to specific apartments).

MikeVolz

Matthew:

If your addresses do include apartment numbers, ESRI has introduced an out-of-the-box (OOTB) locator style to handle these subaddresses at v10.3 and newer. If you have not upgraded to v10.3 yet, you would need to create your own highly customized locator style (I believe there is a customized locator style for 10.1 and above available for download from the geonet site, but it is not supported by ESRI so I would not recommend going this route - If you are interested I could provide the link to the specific geonet thread).

Anonymous User

Thank you Michael and Chris. As I progress with the mapping I'll have to see what makes the most sense. Thanks for your help.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.