Latest Contributions by Bud

[removed] ... View more

Related: Search for the word “Arcade” in this page: (multiple instances) Your Ideas in the December 2021 ArcGIS Online Update Also, see the Arcade developer profile docs: Form Calculation (since Arcade version 1.17) ... View more

Rob, In case you aren’t aware, there is also an Attribute Rules community where you can ask questions like these. ... View more

Related: Code Review: Set polyline M-values to cumulative length of line ... View more

Hi Mike, here's my latest version, in case you're interested. I used your suggestions.   //Script title: Set polyline M-values to cumulative length of line var geom = Dictionary(Text(Geometry($feature))); var paths = geom['paths']; //Using the Equals() function doesn't work as expected. See: Arcade: Editing M-values not treated as change to geometry (https://community.esri.com/t5/arcgis-pro-questions/arcade-editing-m-values-not-treated-as-change-to/m-p/1153917) //if (Equals(Geometry($feature), Geometry($originalfeature)) ) { if (Text(Geometry($feature)) == Text(Geometry($originalfeature))) { console("The geometry has not changed. We don't need to redefine the M-Values.") return } else { //Alternatively, this could be done with the Arcade distance() function. I chose to do the math manually so that the script can be used elsewhere, such as VSCode (for debugging). function pythagoras(x1, y1, x2, y2) { return sqrt(pow(x2 - x1, 2) + pow(y2 - y1, 2)); } var oldX = paths[0][0][0]; var oldY = paths[0][0][1]; var line_length = 0; for (var path_idx in paths) { for (var point_idx in paths[path_idx]) { var newX = paths[path_idx][point_idx][0]; var newY = paths[path_idx][point_idx][1]; //For multi-part features, we want the M-value for additional parts to start at the last M-value from the last part. We don't want to measure the distance *between* parts. //So, for the first vertex in a given part, we will skip calculating the length between vertices. if (point_idx != 0) { line_length += pythagoras(oldX, oldY, newX, newY); } //We can use a negative slice: it will work when there is no Z. paths[path_idx][point_idx][-1] = line_length; oldX = newX; oldY = newY; } } console("The geometry has changed. So we *will* redefine the M-Values.") return { "result": { "geometry": Polyline(geom) } }; }   @JohannesLindner might find this interesting. Cheers! ... View more

@JohannesLindner Fair enough. @KoryKramer, feel free to close. Cheers. ... View more

@JohannesLindner @Thanks, what I meant was: explode a given polyline part into multiple 2-vertex segments (split at each vertex). ... View more

I support this idea (related). @NicholeSalinger, and for anyone else who’s interested: As a last resort, in enterprise GDBs, and depending on the DB type (Oracle, etc), we might have the option of making HTTP calls via the database. For example, Oracle has the UTL_HTTP package that can make HTTP calls from PL/SQL. So in theory, we could use that in conjunction with a database trigger to make a call to an external system. Or make the HTTP call from a database view, and then use that related view in an arcade script: Arcade: Use related DB views as FeatureSets That's far from ideal; it’s complicated, would take some time/effort from the DBA to set up, and would be clunky to manage. But it might work as a very last resort. I’ve seen it used in systems that aren’t configurable (except through the database) for integrations between systems. ... View more

@jcarlson  I updated the idea to clarify what I meant: convert feature vertices to points. Thanks. ... View more