Select to view content in your preferred language

Trace Network Topology errors - how to fix/set null weight values

1215
3
10-03-2024 10:18 AM
Labels (1)
JasperRomero
Occasional Contributor

Hi folks,

I recently started working with Trace Networks and topology in an effort to use Arc Hydro, and I am struggling to understand and correct a very prevalent error. Working in ArcGIS Pro 3.2.

My inputs for the network are a point feature class (storm drain nodes, i.e. inlets, outlets, manholes etc.) and a line feature class (storm drain pipes, i.e. directional lines connecting the nodes).

Initially I had several Stacked Point and Midspan connectivity errors - was able to get past these by switching from Simple to Complex edge connectivity policy and cleaning up duplicate points. 

Now, however, virtually every line in my network has Error type 32:

"Error setting weight values. [This weight cannot be null.]"

I am having a hard time understanding the source of this error, and where/how to correct it. I think I understand that the weights are attributes from the input data used to trace through the network, but I don't completely understand which attributes are selected or how they are applied. I did not see an option in the Create Trace Network GP tool to choose which fields are used for weights. 

I have found some related documentation of the error:
https://pro.arcgis.com/en/pro-app/latest/help/data/trace-network/error-features.htm#

https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/about-error-features.htm

but have not been able to identify how to actually solve the problem.

Mea culpa: I have not worked through every Esri tutorial/example of using and correcting trace network errors (though I have read through and done portions of a few of them) - I am trying to generate a product at work on a tight timeline, so I'm hoping to get some directions straight towards the root of the problem.

Any context, explanations, or suggestions about how to solve this problem and get a trace network suitable for use with Arc Hydro would be so helpful!

Thanks in advance - please request clarification as needed!

3 Replies
geovolve
Occasional Contributor

I'm getting the same error @JasperRomero 

Did you find a solution to resolving error #32?

0 Kudos
JasperRomero
Occasional Contributor

Unfortunately I have not - wound up giving up on this for now. I'm sure I'll try again in six months and probably run into it again, so please let me know if you get to the bottom of it!

0 Kudos
markmorrison1
Emerging Contributor

I recently encountered this same error while deleting and adding fields. The fields were OwnedBy, MaintBy and Material. I reversed the action and validated the UN again but the error persisted. I noticed the error was only on one Asset Group/Asset Type combination. I selected them, recalculated to Unknown/Unknown, validated, recalculated to their original Asset Group/Asset Type and the errors were resolved. I reran all of my subnetwork traces and everything appeared to be fine. Hope this helps someone. 

0 Kudos