Pro 2.4
The Create Locator tool with a Point Address role, bails out on a feature class of roughly 500K address points:
Messages
Start Time: Thursday, July 11, 2019 9:58:35 AM
Start building locator...
Start transforming data...
Start processing Point Address role
Error happened while transforming data
Failed to execute (CreateLocator).
Failed at Thursday, July 11, 2019 9:58:55 AM (Elapsed Time: 19.91 seconds)
Not much to work with with respect to error messages. This data resides in in and enterprise gdb, and it bailed out using the egdb as a source, so I saved it to a fgdb and bailed out there as well. Anyone else using this new approach to creating a locator?
edited to add: the create address locator tool in 2.4 works just fine...
Solved! Go to Solution.
Hi Joe,
That's correct, the Repair Geometry and Check Geometry tools do not work on enterprise geodatabases.
You would only need to script the Repair Geometry tool (Check Geometry just outputs a stand-alone table with any warnings/errors), but be cautious because the Repair Geometry modifies your existing data, so it may be good to script in a back-up of the data as well.
Happy Pioneer Day!
-Eric
Is Null geometry the only cause of the "Error happened while transferring data" message and associated Create Locator tool failure?
Forgot that I needed to add an extra data cleanup step to remove unamatched records from point feature class created by geocoding which by definition have Null geometry. Now it works.