Latest Contributions by Letíciad_Agosto_Miguel_Fonseca

Thanks everyone! ... View more

Hi @SantiagoAvendaño  Have you managed to resolve this issue? I'm attempting to calculate the turbidity index from esri developer page, but I'm encountering an error when saving the image to my portal. Occasionally, the process starts, but the image generated in my portal contains errors. Thanks https://developers.arcgis.com/python/latest/samples/river-turbidity-estimation-using-sentinel2-data-/   ... View more

Hi @ScottGIS  I resolved this by adding my data as an elevation layer in ArcGIS Pro, which automatically enabled the LERC option when I clicked to share:     ... View more

Hello @PavanYadav , first of all, thank you for your attention. Indeed, I noticed some inconsistencies. Here is the stats.txt from my training samples: The .TIFF image I exported from the .ECW file is showing 4 bands, although there are only 3. I re-exported it using the Raster to Other Format geoprocessing tool and now it is right: Now, the statistics for my training samples (62 swimming pools) are as follows:   However, I believe I need more training data and better resources to fine-tune the model. When I tried running the tool, my ArcGIS Pro crashed, and it's not feasible to use 100 epochs and a batch size of 64. I’ll try running it on another server and see if I can successfully fine-tune the model. If you have any more suggestions on how to improve, please let me know.   ... View more

Hi @MikeMillerGIS ! Indeed, the problem was with the vertex. I included the vertex, created the junction and the lateral line, and then ran the update subnetwork. Now, my features are selected in the result. Thank you very much!   ... View more

Thanks a lot @RobertKrisher ! I will take a look at this tutorial! ... View more

Hi @RobertKrisher , Thank you for your answer! We are developing a similar solution to what you suggested. We created a network attribute to leverage the default trace function, enabling us to summarize the entire service connection flow within the trace: At this stage, we aim to summarize the flow by using the asset ID to identify the specific distribution path for each water line, helping us determine if connecting a new customer to the water line is feasible. Can we achieve this with the default tool, or do we need the summary statistics tool? Thanks in advance! ... View more

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‌ ... View more

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. ... View more