We have just migrated an ArcHydro Stormwater File GeoDB to a File GeoDB Stormwater Utility Network v1.4. We have been unable to save Upstream and Downstream elevations for Stormwater Lines. DB is Z enabled with an NAVD 1988 in US-Survey Ft units. XY is NAD83 SP West in US-Survey Ft units. Options: Distance Units are also set to Foot_US. ArcGIS Pro version is 3.5.4. Elevation Z-values are saving to Stormwater Devices.
Then you need to disable the Set Attributes from Z attribute rule. That is overriding your values with the Z of the line.
Edit Vertices tool will set all line points at that edited point with the same Z-values. Is there a different workflow we should follow?
The attribute rule should only fire on create, giving you initial elevation values to drive your slope/analysis. If you are blessed with having more detailed information about each invert that you can use to fine-tune the elevation data on your pipes after that then you should absolutely capture it.
@MikeMillerGIS thoughts?
We figured out our workflow was faulty. We thought the Z-elevations were supposed to be entered into the Attribute table. Now we enter by selecting the line and using the Edit Vertices tool that then updates the Attribute table. That allows us to bring the Z-value rule back into use. However, that has brought up a related issue. A single point can have only a single elevation while with manholes there are multiple elevations. See image from Storm Drain Profile plan sheet:
The invert elevation of the pipe from the catch basin is 746.532 meters. The invert elevation from the stormwater main upstream is 745.668 meters. And the invert elevation from the pipe out downstream is 744.518 meters. So, two out of three pipes will have an incorrect Z-value and an incorrect slope measurement.
If you ever want to turn that attribute rule back on, while still supporting the workflow of manually entering attributes. You would want to add logic to skip over updating the fields if they're already populated.
You have correctly identified the problem and your solution works. Thank you for your advice.
I need to clarify the issue arising upon hitting the "Apply" button.
Before:
After:
None of the three fields have a default value of zero.
The Stormwater pipe was digitized as were the point features in ArcHyrdro originally. A Z value was provided for the manhole. The points and lines are connected. I checked by selecting the pipe and when moving the pipe, it took the points on both ends with it.
If you want to copy the Manhole elevation attribute to the Pipe, then I would look at the Spatial Join Templated Attribute rule. You should be able to configure it for your needs.
https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/attribute-rules-generate-spatial-join
Edit, We do not have an Attribute Rule to set the Z's or attribute of the From/To elevation from the snapped feature. The rule you posted just calculates the slope of the line via the From/To Elevation. There is a rule to Set the From / To elevations from the Z. We rely on ArcGIS Pro and snapping to copy the Z to the geometry. How did you draw the sewer main? Was it snapped to the manhole on create? Did the manhole have a Z?
The Geometry method takes a $feature and returns its geometry.
I recommend you test out this method by putting it in a popup expression on the line layer (have one for the upstream elevation and another for the downstream elevation), then click a few features and see what its outputting.
I'd defer to the data dictionary and @MikeMillerGIS about the elevation field.
2 and 3 verified. Looking at attribute rule, number 1 above. Here it is:
// Assigned To: StormwaterLine// Type: Calculation// Name: Line - Main Slope// Description: Adjusts the slope based on the upstream, downstream, and length of the main// Subtypes: All// Field: slope// Trigger: Insert, Update// Evaluation Order: 4// Exclude From Client: False// Disable: False
// Related Rules: Some rules rely on additional rules for execution. If this rule works in conjunction with another, they are listed below:// - None
// Duplicated in: This rule may be implemented on other classes, they are listed here to aid you in adjusting those rules when a code change is required.// - None
// ************* User Variables *************// This section has the functions and variables that need to be adjusted based on your implementation
// Limit the rule to valid asset groups/subtypes// ** Implementation Note: Instead of recreating this rule for each subtype, this rules uses a list of subtypes and exits if not valid// If you have added Asset Groups, they will need to be added to this list.var asset_group = $feature.assetgroup;var valid_asset_groups = [4, 5, 6, 7]; // Pipe, Open Channel, Culvert, Linear Drain
// ************* End User Variables Section *************
// Limit the rule to valid asset groupsif (!Includes(valid_asset_groups, asset_group)) return $feature.slope;
if (IsEmpty($feature.UPELEV) || IsEmpty($feature.DOWNELEV)){return $feature.slope;}if (IsEmpty(Geometry($feature)) || Length(Geometry($feature)) == 0){return $feature.slope;}return ABS(($feature.UPELEV - $feature.DOWNELEV)/Length(Geometry($feature)));
Under Field names, the "Geometry" data type is named "Shape". Should that be used in lieu of "$feature", above? There is also a Double Type Field st_length(SHAPE) that is my other choice.
Also, under Stormwater Device, the Field "elevation" is a short Integer instead of a Double. Not sure why? Is this elevation field intended for surface or invert/bottom?
Can you please verify three things:
The attribute rules remain unchanged from the porting over of the Napierville schema. Values show as zero although I have tried a variety of numbers ranging from single digit to four digits. I simply assumed Stormwater Utility Network v1.4 had this baseline covered. I have attached a sample selected line with attributes shown in three images. All lines and points in this extent passed validation.
Can you post a screenshot of what attributes or values you are expecting to be updated on the lines class? Do you have any attribute rules written to maintain these attributes as you are creating or updating features?
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
