I am trying to calculate the geometry for my Length_3D field in my Pathways and Transition feature classes in a Network dataset we are using for our Indoors routing network. We previously have done this many times without any issue, but recently (the last 2-3 weeks) as we have made a few updates, I always get this error when running the tool, "SystemError: <method 'updateRow' of 'da.UpdateCursor' objects> returned NULL without setting an exception", on all 12 network datasets we currently manage.
Currently using Pro 3.5.2.
Things I have tried:
-Exporting features to a new feature class - This works but once I create/build the network, make an edit and try to calculate it again, it fails.
-Repair Geometry tool - with the option to delete NULL geo checked. Runs successfully, but Calculate Geometry tool still fails.
-Compress Geodatabase tool - completely crashes the program every time.
We use this field in our Network to calculate the distance and travel time. For the Pathways, I could probably get away with just using the shape_length field but not for the Transitions feature, as those are mostly stairs/elevators that have a much longer 3D length than the shape_length field calculates.
My solution right now is to export the features, calculate geometry, recreate the network dataset and build the network. This works for now, but is far from ideal as we will regularly need to make updates in the upcoming months as we deploy this and find routes that are incorrect/not ideal.
Any other options to try would be greatly appreciated.
Hey @MollyE
When you say a few updates, do you still have a backup of the program prior to your changes to now? If so, I would bring that version back, and see if everything is working on that version, if so, slowly start bringing your changes back to see if anything had caused it.
Next, within those 2-3 weeks, was an ArcGIS Pro update in that time frame as well? For example did you go form 3.2 to 3.5.2? If so, is it possible to roll back or use a coworkers machine with a different version?
To me this appears that something either changed in the program that would cause this or maybe ArcPro itself. I've found this post as well:
Could you post a snipped of where this is happening?
Cody
Thanks for the reply, Cody.
I have tried using data that has not changed since it previously worked, and it also fails. It could possibly be an issue of going from 3.5.1 to 3.5.2, but I believe I have ran it successfully since then, as it's been about 6 weeks since my last update. We try to keep the program as up to date as possible. I could try going back a version, but would rather exhaust all my other options first as I would have to get my orgs IT involved, and we are using some features that are only available in 3.5 for other projects.
What other snip would you like to see? I'm not sure what else to post other than my tool parameters and the error I receive. This is not a python script I created, it's a prebuilt arcgis pro tool.
Hey @MollyE
I can definitely understand waiting until all the other options are exhausted first, my own IT can be a hassle to get things going!
For some reason I was under the impression this was a custom built tool, I'm away from my machine currently but I'll give it a shot on my 3.5.2 instance as well and see if I can get it recreated!
Cody
Thanks, Cody I appreciate your help. I did find the .py file for the tool, and here is the spot where it is saying the error happens (line 213). I don't think I can/should edit this at all but maybe it will make sense to you where something is going wrong. Maybe I can just create my own tool from this if there some issue I could fix? I know a little python but not enough to make sense of this yet lol.
The first line mentioned mentions in the error (379) is just the final command to run the script, but I can attach that too if you would like to see it.
Hey @MollyE
I'm back at my machine, and I'm unable to replicate this so far, I've tried to use the same and different coordinate systems but no luck as of yet. I was curious if you're able to export a few features from the layer, and see if you can do a small calculate field on that information? My assumption is that there is a key point of information missing from your layer or a single feature and it's causing this issue, but so far my tests can't find it just yet! It's definitely something odd.
Cody
Hi @MollyE
Have you tried using the Calculate geometry Attributes tool instead of Calculate Geometry?
Calculate Geometry Attributes (Data Management)—ArcGIS Pro | Documentation
Check for Z-value integrity. Since you are calculating 3D length are there any corrupted or missing Z-values? You can use the Add Z information tool to inspect Z-values.
Have you tried on a new blank project? Have you tried to rebuild the network dataset with a minimal schema adding in fields and attributes to trigger a failure?