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; } } }

Create Locator for Street Address Role not working Pro 2.5

StephanieBosits

I am attempting to create a street address locator via the Create Locator tool in ArcGIS Pro 2.5. For now in an attempt to just get the tool to run I am only filling in the required fields and I get the generic error:

Error happened while transforming data

Failed to execute (CreateLocator).

I have seen in other posts that this can often be caused by a null geometry in the data. I have run check geometry 
and repair geometry on my data just in case and there is no null geometry in the data.

I have tried running this tool with multiple different versions of my road centerline data (slightly different 
schemas and database sizes) and have never gotten it to run successfully. 

I have been able to create a locator using this tool for my address points with a point address role.

Screenshot of small test area below, does anyone have any thoughts?

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

FentonCheng_-_DIT

I'm getting the same error too on my street centerline data. I also tried rebuilding the locator with the original data and it also failed.

Robert_LeClair

Stephanie - in reviewing some internal threads, I found 2 possible workflows to resolve this error message.

1. Simplify Line - run the Simplify Line Tool on the line feature class and use the output of the 'Simplify Line Tool' in the 'Create Locator Tool."

2. Export as a shapefile - export the line feature class to a shapefile and use the shapefile result in the 'Create Locator Tool.'

Something else to try is to clear the Display Cache - go to the Projects tab->Options->Display and check the Clear cache checkbox. Click OK.

What is the result? Please advise.

StephanieBosits

I ended up opening a case with ESRI and yes the advice given was to export to a shapefile. This worked for me. I was told this bug should be addressed in Pro 2.6. Thanks for your help Robert!

JoeBorgione

My suspicion is you have null geometries or empty geometries in your street data. See this post of mine from Dec 2019. Interesting that Tech Support is selling you on a bug; I've built several street role locators with 2.5 and never had a problem.

ShanaBritt

In looking at the data in the screenshot you provided and seeing that the Check and Repair Geometry tools had no affect on being able to build the locator with the Create Locator tool, I suspect that there are true curves or arcs in the centerline file, perhaps a cul-de-sac, that is causing the failure. Since curves are only supported in geodatabases, exporting the feature class to a shapefile simplifies the problematic features. You can also run the Densify tool with the Offset Densification Method to simplify the lines.

I would also check for any multipart features that may need to be exploded using the Multipart to Singlepart tool, then use the new feature class to build the locator. Run either the Add Geometry Attributes or Calculate Geometry Attributes tool to add the 'Number of parts' Geometry Property to the reference data. A feature with more than one part is considered a multipart feature.
Note: The tools add a new field named 'PART_COUNT' to the Input Features of the tools.

StephanieBosits

Thank you, very helpful I know there are true curves in the database so I suspect that is what is causing the issue, I will test that out. Thanks again!

PhilLarkin1

Hello- Were you given a bug number that you can share?

PhilLarkin1

A workaround that might be a solution for you, assuming you store your data in MSSQL and have geometry shape type (vs sdebinary) is to use the Reduce method in a query layer. This worked for me.

It it hard to say if it will eliminate every curve as it will return several types. You could tweak the tolerance if it didn't work the first time.

Reduce() returns a LineString, CircularString, or CompoundCurve instance for CircularString instances. Reduce() returns either a CompoundCurve or LineString instance for CompoundCurve instances.

Ideally you wouldn't need to do this. Hopefully a valid solution comes with 2.6.

StephanieBosits

BUG-000127864. This issue seems to have been resolved in Pro 2.6

JoeBorgione

take a look here: https://community.esri.com/message/935520-true-arcs-geocoding-and-other-musings

Ú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.