Latest Contributions by Bud

Migrated from a duplicate idea: I have calculation attribute rules that only needs to be run if the geometry is edited. Example: If a new feature is created or if an existing feature's geometry is edited, then: Redefine the M-Values by setting them to the cumulative length of the line. It's not necessary to run those kinds of calculation attribute rules if only the non-spatial fields get edited. And there are scenarios where unnecessarily running the attribute rules causes slow performance. Could an optional setting be added to calculation attribute rules that would let us only run the rule if the geometry has been changed? ... View more

Possible workaround: Create an attribute rule that compares the true length vs the densified length. If there is a difference, then there is a curve, so prevent the user from saving the edit. More info here: https://community.esri.com/t5/arcgis-pro-ideas/hascurve-arcade-geometry-property/idc-p/1149449/highlight/true#M18873 ... View more

In the meantime, I wonder if this would be a possible workaround: 1. Create a field in the feature class called HAS_CURVES. 2. Populate the field in real-time/when a user creates or modifies a feature -- using a Calculation Attribute Rule. Compare $feature.shape_length, which is the true length, including true curves vs. Length($feature), which is the pre-densified length, where true curves have been converted into straight segments. https://i.stack.imgur.com/ilJrg.png If there is a difference between those two values, then that tells us that the line has curves. Use a Calculation Attribute Rule to set the HAS_CURVES field to "Y". 3. That field would be available to SQL. So we could query on it as needed. Disclaimer: It's possible that comparing the those lengths might not work in all scenarios (due to rounding complications, etc.). Testing would be needed. As the idea suggests, it would be a lot more robust to have a SDE.ST_HasCurves() function in ST_GEOMETRY. Related:  Idea: hasCurve Arcade geometry property Calculate length of line without using length function (and without densifying curves) Select SDE.ST_GEOMETRY polylines that have arcs? ... View more

@CraigWilliams  Thanks! In the meantime, I wonder if this might be a valid workaround: Compare $feature.shape_length, which is the true length, including true curves... vs. Length($feature), which is the pre-densified length, where true curves have been converted to straight segments. If there is a difference between those two values, then that tells us that the line has curves. What do you think? Do you see any issues with that approach?   ... View more

Thanks! I'm wondering if the core issue is that the geometries in Arcade get automatically densified (at least, I think they do). Get the true vertex count (Arcade) Arcade Polyline paths documentation: Explain that lines get automatically densified   Additionally, I think I might have found a workaround. Instead of using Length($feature) which gives the wrong length, I think we can use $feature.shape_length  which gives the right length. I wonder if the reason Esri auto-densifies geometries is for the scenario that you mentioned — generalizing in different scales when used in feature services. Maybe that's the why here. Or maybe, it's just because true curves are a pain, and are easier to deal with if they're always automatically densified. Related: Calculate length of line without using length function (and without densifying curves) ... View more

We're aware of the following blurb in the docs — Arcade Geometry Functions: Also note that geometries fetched from feature services, especially polylines and polygons, are generalized according to the view's scale resolution. Be aware that using a feature's geometry (i.e. $feature) as input to any geometry function will yield results only as precise as the view scale. Therefore, results returned from geometry operations in the visualization and labeling profiles may be different at each scale level. Use these functions at your discretion within these contexts. But that doesn't tell us anything about us the fact that true curves get densified, regardless of scale. And in my case, I'm not using feature services, I'm using FCs directly from a FGDB or EGDB. So that blurb doesn't apply, yet I'm still seeing the pre-densification behavior.   ... View more