The following profiles added a new global,
$originalFeature, which represents the original state of the feature executing the Arcade expression.
- Added an additional signature that allows users to parse stringified JSON as an Arcade Dictionary.
- Added support for FeatureSet inputs.
- Now implemented in the Popup profile with a modified signature. You are now required to provide a reference to the portal where the item belongs.
The function documentation now displays multiple signatures for functions that have overloaded parameters. This includes new documentation for the following functions:
The following functions were updated to support an array of points as inputs.
The following functions were updated to support FeatureSet inputs:
- The parameter order of Contains and Within functions were updated to properly work for FeatureSets and standalone geometries.
FeatureSet support in popups and attribute rules
FeatureSet is a new data type that gives you access to other features in the same layer, feature service, or map as the feature executing an Arcade expression. This functionality is only available in the Popup and Attribute Rule profiles.
We introduced three new global variables in these profiles:
$layer- A FeatureSet containing all features in the same layer as the
$feature. This only applies to feature layers.
$map- A collection of layers in the same map as the
$datastore- A collection of layers in the same feature service as the
FeatureSets allow you to write expressions that return a result based on the feature's relationship with other features in the map. For example, you can compare the value of a feature's field to the statistics of the same field for all features in the layer.
// returns the difference between the feature's 'population' and the average value of `population` in the dataset $feature.population - Mean($layer, 'population');
You can chain functions that support FeatureSet.
var sensitiveAreas = FeatureSetByName($map, 'Sensitive Land', ['LandType'], true); var affectedLandPoly = Geometry($feature); var countAreas = Count( Intersects( Filter( sensitiveAreas, "LandType='Arable'"), affectedLandPoly) );
You can also substitute Arcade variables in functions that take SQL92 expressions as a parameter using the
var averageValue = Average($layer, 'POPULATION'); var result = Filter($layer, 'POPULATION > @averageValue');
- Attribute Rule Calculation
- Attribute Rule Constraint
- Attribute Rule Validation
- Feature Z
- Field Calculate
Existing functions that support FeatureSet
Casting Feature to Geometry
For your convenience, we added support for internally casting features to geometries in all geometry functions. That means you can directly pass a feature (e.g.
$feature) to any parameter that
accepts Geometry types.
// At Arcade 1.4, you can pass a feature directly to any geometry // function, which internally casts the feature as a geometry object AreaGeodetic( $feature, 'square-meters' ) // This supersedes the previous workflow, which required you to // cast the Feature to a Geometry yourself // required syntax at Arcade 1.3 AreaGeodetic( Geometry($feature), 'square-meters' )
Arcade expressions can now be executed in the following profiles:
These profiles allow you to write expressions for attribute rules in ArcGIS Pro.
We added several new geometry functions that allow you to perform geometric operations in any of the following categories:
- Testing topological relationships
See the updated overview of Geometry Functions for more information and the new functions listed below.
Many of the geometry functions, such as the overlay and testing functions, require more than one input geometry. In the current release of Arcade, you can manually construct geometry objects as needed within the expression. For example, you can calculate the distance from one hard-coded point to all points in a layer. In a future release, we will provide methods that allow you to access other geometries within the same layer and features in other layers.
The popup profile was added, allowing users to define expressions that will evaluate and display values calculated on the client when the popup displays in the view. Users can reference Arcade expressions with placeholders that will be replaced by expression values when the popup is opened. See the individual ArcGIS SDKs for examples of how this works within applications.
Feedback on this topic?