Latest Contributions by Bud

Could an Arcade function be added to do the following: Snap a point to a polyline — but snap it mid-segment, not just to the closest vertex. The function would return the snapped point — as well as return the ID of the polyline the point was snapped to. Thanks. ... View more

I want to find all ArcGIS communities that have the ‘Arcade’ label — so that I can subscribe to those labels. Examples: - ArcGIS Pro Community - [Arcade] - ArcGIS Online Community - [Arcade] - Others How can I search all communities for a certain label? ... View more

It would be helpful if there were an Arcade function for setting M-values of polyline vertices. For example, set the M-values of a line to the cumulative distance of the line.   ... View more

Arcade: What’s the most succinct way to get the endpoint coordinates of multi-part polyline? Related: Idea: Arcade Endpoint() function ... View more

  It would be great if we could use related DB views as FeatureSets in Arcade scrips (just like we do with related FCs).   ... View more

The Arcade docs have examples for the GroupBy() function: Returns the count and the average height of each tree type var treeStats = GroupBy($layer, [ // fields/expressions to group statistics by { name: 'Type', expression: 'TreeType'}, { name: 'Status', expression: 'TreeStatus'} ], [ // statistics to return for each unique category { name: 'Total', expression: '1', statistic: 'COUNT' }, { name: 'AvgHeight', expression: 'Height', statistic: 'AVG' }, { name: 'MaxPercentCoverage', expression: 'CoverageRatio * 100', statistic: 'MAX' } ] ); // treeStats contains features with columns Type, Status, Total, AvgHeight, MaxPercentCoverage // Each unique tree type (combination of type and status) will have a count, average height, and maximum value of percent coverage That GroupBy() stuff can get messy in a hurry. It would help if we could see what the SQL would look like, right in the docs. (possibly as a comment in the Arcade code example)   ... View more

When writing Arcade scrips that make queries to the DB: It would help to see what SQL is being used, by outputting the SQL to the console(). For example, I’m an SQL guy, yet I find the GroupBy() function easy to mess up. It would help if I could easily see the SQL that’s being sent to the DB — to make sure the query is right. Could Esri consider making the SQL text available as a variable, so that we can output it to the console for debugging purposes? ... View more

Could Esri consider adding a new function: EqualsMZ() - Similar to the Equals() function, but it not only tests the XY geometry, but also any M or Z values that may exist. Related: Arcade docs: Equals() function doesn’t consider M-values Credit for this idea goes to @DuncanHornby  ... View more

Is there a way to subscribe to a specific tag in a community? For example, I want to get weekly or daily email notifications regarding posts about Arcade. Similar to what we can do with GIS.StackExchange. How can I do that? Thanks. ... View more

As far as I can tell, the Equals() function doesn’t consider M-values when comparing geometries. See: Arcade: Editing M-values not treated as change to geometry  If that’s the case, then could a blurb be added to the Arcade docs that explains this? I know the docs hint at it with the “geographically equivalent” wording, but I think it could be clearer. It might also help to explain whether Z-values get considered or not, too.   ... View more

ArcGIS Pro 2.9: I have a Arcade calculation attribute rule that checks if the geometry of a feature was changed during an edit: if (Equals(Geometry($feature), Geometry($originalfeature))) { console("geometry changed = no"); return {"result": {"attributes": {"geometry_changed": 'no' }}} } else { console("geometry changed = yes") return {"result": {"attributes": {"geometry_changed": 'yes' }}} } The intent is: If the geometry was changed, then it sets a geometry_changed field to "yes". If not, it sets the field to "no". The attribute rule works as expected in most cases. For example, in the Edit Vertices window, if I manually change an X or Y coordinate using the keyboard, the field will be flagged as "yes", as expected.  However, if I manually change the M-value in the Edit Vertices window using the keyboard, the field will be flagged as "no", which is not expected. The same thing happens when I use the Drop Measures tool: Question: Why don't M-value edits get flagged as a change to the geometry? Thanks.   ... View more