topic Re: Change symbol rotation - Water utility network in Water Utilities Questions

Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Tue, 31 Mar 2020 19:59:55 GMT

Hello Everyone!

I am trying to rotate some symbols in my Utility Network PRO project (using ESRI template: water distribution network editor) but I can't change the ones that already have numbers.

Example: I want to change the rotation from 119 to 29, calculating on field calculator it runs, but it brings me back the same number (119). (Image attached)

Any help will be very usefull 😃

Regards,

Layane Beatriz Silva Loti‌

Antonio Marcos Pires Martins‌

Re: Change symbol rotation - Water utility network

PaulLeBlanc1 — Tue, 31 Mar 2020 20:07:15 GMT

There might be an attribute rule that is resetting it based on the orientation of the line it intersects with.

Re: Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Tue, 31 Mar 2020 21:14:40 GMT

Hi Paul,

We are awere about the rule attribute, in fact we calculated the rotation for the ones with the value 0 in the attribute table using the numbers that meet the rule criteria.

But how could I edit the ones already populated? Do you know if Is there a way to "turn off" the rule and set to 0 again?

Thank you very much!

Re: Change symbol rotation - Water utility network

PaulLeBlanc1 — Tue, 31 Mar 2020 21:18:43 GMT

You can disable the rule from a GP tool or design view.

Ideally though, if you want to override what the rule is setting, you'd check if there is a value in the field before writing a value to it.

Re: Change symbol rotation - Water utility network

MikeMillerGIS — Tue, 31 Mar 2020 22:20:12 GMT

Set the values to null

Re: Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Wed, 22 Apr 2020 13:18:49 GMT

Hi Michael and Paul,

It worked setting values to 0 and them using the calculate field with the attribute rule enabled.

Other issue is that our fittings are not following the "right" line to rotate, as the tap in our example.

We think this problem might be related to which line the fitting is using as a reference, is that right?

Any ideia how to fix this problem?

Thanks!

Layane Beatriz Silva Loti‌

Re: Change symbol rotation - Water utility network

MikeMillerGIS — Wed, 22 Apr 2020 13:28:34 GMT

The symbol might need to be rotated in the layer. Is it always this way, for every tap?

Re: Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Wed, 22 Apr 2020 14:09:04 GMT

The symbols are already rotated in this example. Yes, it is always this way for taps.

Re: Change symbol rotation - Water utility network

MikeMillerGIS — Wed, 22 Apr 2020 14:52:34 GMT

Then just rotate the symbol in the symbology of the layer

Re: Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Wed, 22 Apr 2020 15:22:39 GMT

I think I was not clear before, sorry about that. I have tap's in different directions, so If I change the rotation of the symbology, it is applied for all of them.

Thanks!

Re: Change symbol rotation - Water utility network

MikeMillerGIS — Wed, 22 Apr 2020 16:20:10 GMT

Will have to debug the rule and build out the scenarios. Are the mains split at that location, what are the lines digitized direction. Is this the sample data?

Re: Change symbol rotation - Water utility network

MikeMillerGIS — Wed, 22 Apr 2020 16:24:22 GMT

Is the rotation set to Geographic or Arithmetic? That looks like the issue actually

Re: Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Wed, 22 Apr 2020 17:54:56 GMT

Hi Michael, yes this is my sample data.

The mains are not Split (as you can see from selection) and we set to Arithmetic rotation because of the attribute rule. It seems to be following the line direction (Distribution main), but we needed it to be set to the service line.

Re: Change symbol rotation - Water utility network

MikeMillerGIS — Wed, 22 Apr 2020 18:05:47 GMT

Can you verify this is the rule you are using?

https://github.com/MikeMillerGIS/arcade-expressions/blob/master/attribute_rule_calculation/RotateFeatureByIntersectedLine.md

Based on the logic, you should be around this section of the code:

else if (Count(angles) == 2) {

// If the feature is midpan of the first line, return the angle of the second line

if (angles[0]['type'] == 'mid')

return angles[1]['angle'];

// If the feature is midpan of the second line, return the angle of the first line

else if (angles[1]['type'] == 'mid')

return angles[0]['angle'];

Can you create a pop up on taps and use this rule. Then you can add to the return statements to see what part is being users?

Such as

else if (Count(angles) == 2) {

// If the feature is midpan of the first line, return the angle of the second line

if (angles[0]['type'] == 'mid')

return “Count 2, angle 1 is mid” + angles[1]['angle'];

// If the feature is midpan of the second line, return the angle of the first line

else if (angles[1]['type'] == 'mid')

return Count 2, angle 2 is mid” + angles[0]['angle'];

Re: Change symbol rotation - Water utility network

Letíciad_Agosto_Miguel_Fonseca — Thu, 23 Apr 2020 14:12:51 GMT

Hi Michael,

It worked using the rule with multiple lines. I set everything to null using the calculate field and changed the symbology layer.

But when I insert new features, it is returning 0 and I have to calculate null values to trigger the rule. I saw there is an issue with Arcade returning 0 instead of null :BUG-000119064: Calculating a value to null using Arcade returns 0..

This is how the code looks like now:

// This calculation attribute rule intersects a line layer and based on the number of
// intersected features, calculates the angle for the point
// Set to true if the rotation setting is set to geographic in the layer properties
var geographic_rotation = false;
// Set the counter clockwise spin angle used for the symbol in the symbology options
var symbol_flip_angle = 0
// Return if a value is already set, to recalculate an angle, the field must be set to null
if (IsEmpty($feature.symbolrotation) == false) {
return $feature.symbolrotation;
}
else if ($feature.symbolrotation == 0) {
return null;
}
// Create a feature set to the line layer
var lineClass = FeatureSetByName($datastore, "L515Water_Line", ["objectid"], true);
// Find the intersecting lines
var lines = Intersects(lineClass, $feature);
//If no lines intersect, return the original value
if (Count(lines) == 0) {
return $feature.symbolrotation;
}
var diff_tol = 5;
// Variable to store all found angles
var angles = [];
// Store the features geometry
var feature_geometry = Geometry($feature);
// Loop over all intersecting lines and find their angles
var angle_type;
var angle_value;
for (var line in lines) {
// Buffer and create an extenf of the point by a small amount to extract the segment
var clip_area = Extent(Buffer($feature, .01, "meter"));
// Clip the line by the extend and get the first line segment
var segment = Clip(line, clip_area)["paths"][0];
// The features location is on the start of the line, get the angle from the feature to the end vertex
if (Equals(segment[0], feature_geometry)) {
angle_type = 'from'
angle_value = Round(Angle(feature_geometry, segment[-1]), 0)
}
// The features location is on the end of the line, create a new segment from the feature to the start vertex
else if (Equals(segment[-1], feature_geometry)) {
angle_type = 'to'
angle_value = Round(Angle(feature_geometry, segment[0]), 0)
}
// The features location is midspan of the segment, use the angle of the segment
else {
angle_type = 'mid'
angle_value = Round(Angle(segment[0], segment[-1]), 0)
}
if (geographic_rotation == true) {
// Convert Arithmetic to Geographic
angle_value = (450 - angle_value) % 360;
}
// Add 180 to match 0 rotation in the TOC
// Add user specified spin angle if their symbol is rotated
angle_value = (angle_value + 180 + symbol_flip_angle) % 360;
angles[Count(angles)] = {'angle': angle_value, 'type': angle_type};
}

// If only one angle, return that value
if (Count(angles) == 1) {
// If the point is midspan, flip to match symbol as it if was on the end point
if (angles[0]['type'] == 'mid')
{
return (angles[0]['angle'] + 180) % 360;
}
return angles[0]['angle'];
} else if (Count(angles) == 2) {
// If the feature is midpan of the first line, return the angle of the second line
if (angles[0]['type'] == 'mid')
return angles[1]['angle'];
// If the feature is midpan of the second line, return the angle of the first line
else if (angles[1]['type'] == 'mid')
return angles[0]['angle'];
// If the feature is at the end point of both lines, return the angle of the first line
else if (angles[0]['type'] == 'to' && angles[1]['type'] == 'to') {
return angles[0]['angle'];
}
// If the feature is at the start point of both lines, return the angle of the first line
else if (angles[0]['type'] == 'from' && angles[1]['type'] == 'from') {
return angles[0]['angle'];
}
// If the feature is at the start point of the first line and end of the second line, return the second line
else if (angles[0]['type'] == 'from') {
return angles[1]['angle'];
}
// If the feature is at the start point of the second line and start of the second line, return the first line
return angles[0]['angle'];

} else if (Count(angles) == 3) {
// Flatten the angles to ignore direction
var flat_angle1 = angles[0]['angle'] % 180;
var flat_angle2 = angles[1]['angle'] % 180;
var flat_angle3 = angles[2]['angle'] % 180;
// Create differences between angles
var angle_dif_a = Abs(flat_angle1 - flat_angle2);
var angle_dif_b = Abs(flat_angle1 - flat_angle3);
var angle_dif_c = Abs(flat_angle2 - flat_angle3);
// If difference between line 1 and 2 is below the tolerance, meaning the lines follow the ame plane, return the
// third line
if (angle_dif_a <= (diff_tol * 2) || angle_dif_a >= (180 - (diff_tol * 2))) {
return angles[2]['angle'];
}
// If difference between line 1 and 3 is below the tolerance, meaning the lines follow the ame plane, return the
// second line
else if (angle_dif_b <= (diff_tol * 2) || angle_dif_b >= (180 - (diff_tol * 2))) {
return angles[1]['angle'];

}
// If difference between line 2 and 3 is below the tolerance, meaning the lines follow the ame plane, return the
// first line
else if (angle_dif_c <= (diff_tol * 2) || angle_dif_c >= (180 - (diff_tol * 2))) {
return angles[0]['angle'];
}
// Return first if not covered above
return angles[0]['angle'];
}
// All other cases, the first feature is returned
else {
return angles[0]['angle'];
}

Layane Beatriz Silva Loti‌