Latest Contributions by Bud

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

@JohannesLindner  Good points. Regarding versioning: I suspect that versioning with the option to move edits to base could solve some of the issues you mentioned. Regarding error handling:  I believe it's possible to put error handling in Oracle PL/SQL triggers...and then that error message gets returned to the ArcGIS application (such as ArcGIS Pro).    IF v_upd_row = 0 THEN raise_application_error ( -20001, 'a custom message that pops up in ArcGIS Pro'); END IF; That error message would be displayed in a popup message in the application. It'd be the same kind of message that you'd get for any other database-related error. Source: Prevent deletes in a versioned table at the database level By the way, if you're a data owner, the data owner likely has CREATE TRIGGER privileges. So in a pinch,  you could probably create triggers if you needed to. But it sounds like you don't. You could install an SQL client or you could execute SQL statements using the ArcSDESQLExecute ArcPy class. I just thought I'd mention that...for anyone else who might be reading this post. ... View more