(Required)

The input features that will have a field added and calculated.

Syntax: As described in Feature input, this parameter can be one of the following:

• A URL to a feature service layer with an optional filter to select specific features
• A URL to a big data catalog service layer with an optional filter to select specific features
• A feature collection

//REST web example
{"url": "https://myportal.domain.com/server/rest/services/Hosted/hurricaneTrack/FeatureServer/0", "filter": "Month = 'September;"}

//REST scripting example
"inputLayer": {"url": "https://myportal.domain.com/server/rest/services/Hosted/HurricaneTrack/FeatureServer/0", "filter": "Month = 'September'"}

(Required)

A string representing the name of the new field. If the name already exists in the dataset, a numeric value will be appended to the field name.

//REST web example
MyNewField

//REST scripting example
"fieldName": "AccumulatedValues"

(Required)

The type for the new field.

Values: Date | Double | Integer | String

//REST web example
Double

//REST scripting example
"dataType": "Integer"

(Required)

An Arcade expression used to calculate the new field values. You can use any of the Date, Logical, Mathematical, or Text functions available with Arcade expressions.

//REST web example
$feature["Field1"] + abs($feature["Field2"])

//REST scripting example
"expression": "$feature[\"Field1\"] + abs($feature[\"Field2\"])"

A Boolean value denoting if the expression is track-aware.

Values: true | false

//REST web example
true

//REST scripting example
trackAware: "false"

(Required if trackAware is true)

The fields used to identify distinct tracks. There can be multiple trackFields. trackFields are only required when trackAware is true.

//REST web example
AircraftID

//REST scripting example
trackAware: "AirID,DepartureCity"

(Optional)

A time boundary allows you to analyze values within a defined time span. For example, if you use a time boundary of 1 day, starting on January 1, 1980, tracks will be analyzed one day at a time.

The time boundary parameters are only applicable if the analysis is trackAware.

//REST web example
2

//REST scripting example
"timeBoundarySplit": 1

(Optional)

The unit applied to the time boundary. timeBoundarySplitUnit is required if a timeBoundarySplit is provided.

//REST web example
Weeks

//REST scripting example
"timeBoundarySplitUnit": "Days"

(Optional)

A date that specifies the reference time to align the time boundary to, represented in milliseconds from epoch. The default is January 1, 1970, at 12:00 a.m. (epoch time stamp 0). This option is only available if the timeBoundarySplit and timeBoundarySplitUnit are set.

//REST web example
9466835800000

//REST scripting example
"timeBoundaryReference": 946684800000

(Optional)

The task will create a feature service of the results. You define the name of the service.

//REST web example
myOutput

//REST scripting example
"outputName": "myOutput"

The context parameter contains additional settings that affect task execution. For this task, there are four settings:

• Extent (extent)—A bounding box that defines the analysis area. Only those features that intersect the bounding box will be analyzed.
• Processing spatial reference (processSR)—The features will be projected into this coordinate system for analysis.
• Output spatial reference (outSR)—The features will be projected into this coordinate system after the analysis to be saved. The output spatial reference for the spatiotemporal big data store is always WGS84.
• Data store (dataStore)—Results will be saved to the specified data store. The default is the spatiotemporal big data store.

{
"extent" : {extent},
"processSR" : {spatial reference},
"outSR" : {spatial reference},
"dataStore":{data store}
}

The response format. The default response format is html.

Values: html | json