Latest Contributions by Bud

@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

Edit: Disregard ... View more

On closer inspection, it looks like Arcade automatically densifies polyline paths (converts true curves to straight segments). Related: https://community.esri.com/t5/arcgis-pro-ideas/get-the-true-vertex-count-arcade/idi-p/1148911/jump-to/first-unread-message If that's the case, then densifying by angle might not be necessary. ... View more

ArcGIS Pro Version 2.9.32739 (including patch #1). Windows 10 ... View more

Thanks! I happen to be using a file geodatabase directly, not a feature service. Any idea if that blurb applies to FGDBs? ... View more

If for some reason that midpoint expression doesn't work, this might be an option: Buffer the line and get the centroid of the resulting polygon. It's kind of like a "poor man's midpoint". If I recall, that works ok. But I think I remember the point not being the exact midpoint of the line. I forget what the specific issue was. It's probably good enough for most use cases though... ... View more

I'm not sure if this will be helpful or not, but I'll post it anyway: In similar situations where we don't have a Midpoint() function, such as in the St_Geometry spatial type in EGDBs, we've used the following hack: Buffer the line and get the centroid of the resulting polygon. It's kind of like a "poor man's midpoint". If I recall, that works ok. But I think I remember the point not being the exact midpoint of the line. I forget what the specific issue was. It's probably good enough for most use cases though...   ... View more