topic Reverse Geocoding and keep original point feature class with address assigned in ArcGIS Pro Questions

Reverse Geocoding and keep original point feature class with address assigned

TimHayes3 — Tue, 23 Jul 2024 18:08:35 GMT

I am using Pro 3.3.1 and have created a Locator to use for Reverse Geocoding. I have 500 points I want to assign the street address to. The address assigned to each point would be interpolated from the address range in the street centerline. I was able to successfully reverse geocode with the Locator, but it creates a new point feature class.

How can I reverse geocode and not create a new point feature class? I need to assign the addresses to the existing point feature class.

Re: Reverse Geocoding and keep original point feature class with address assigned

BobBooth1 — Tue, 23 Jul 2024 19:38:50 GMT

You could use a unique ID for each input point and join the reverse geocoding output back to the original points. Afterward, add a field to the attribute table and calculate the address info to it, then drop the join.

Re: Reverse Geocoding and keep original point feature class with address assigned

AlexanderVidekaVaughan — Thu, 17 Oct 2024 13:39:40 GMT

Hi Bob,

This is a great workaround to get the result Tim is looking for. It would be great if the Reverse Geocode tool had a checkbox property 'do not adjust geometry of inputs' of some sort to remove the need for these extra steps.

Here is my use case: I have city assets in the boulevard (hydro poles, signs, hydrants etc) that decision makers would like the nearest street address for.

It doesn't make much sense for these inputs to be stacked onto buildings as part of the reverse geocoding workflow.

Re: Reverse Geocoding and keep original point feature class with address assigned

BobBooth1 — Thu, 17 Oct 2024 13:54:27 GMT

Hi Alexander,

Have a look at this thread in Ideas:

https://community.esri.com/t5/arcgis-pro-internal-ideas/arcgis-pro-reverse-geocoding-add-the-geocoded/idi-p/1418930

Is this what you're looking for? It looks as though it has been implemented for Pro 3.3.

If not, you might consider posting your own request in Ideas.

Best,

Bob