(Required)

The time-enabled point features from which dwell locations will be found.

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)

The fields used to identify distinct tracks. There can be multiple trackFields.

//REST web example
Hurricane Name

//REST scripting Example
"trackFields": "BoatName, ConvoyID"

(Required)

The method used to calculate distances between points. There are two methods from which to choose: Planar and Geodesic. The Planar method joins points using a planar method and will not cross the international date line. This method is appropriate for local analysis on projected data. This is the default. The Geodesic method joins points geodesically and will allow tracks to cross the international date line. This method is appropriate for large areas and geographic coordinate systems.

//REST web example
Geodesic

//REST scripting example
"distanceMethod": "Planar"

(Required)

The dwell distance tolerance is the maximum distance between points to be considered in a single dwell location.

Dwell locations are determined using distance and time (timeTolerance).

//REST web example
12

//REST scripting example
"distanceTolerance": 5.5

(Required)

The unit of the distanceTolerance.

//REST web example
Kilometers

//REST scripting example
"distanceToleranceUnit": "NauticalMiles"

(Required)

The dwell time tolerance is the minimum time duration of a dwell to be considered in a single dwell location.

Dwell locations are determined using distance (distanceTolerance) and time.

//REST web example
7

//REST scripting example
"timeTolerance": 12

(Required)

The unit of the timeTolerance.

//REST web example
Days

//REST scripting example
"timeToleranceUnit": "Hours"

(Optional)

A list of field names and statistical summary types you want to calculate. Note that the count of points in a dwell is always returned.

By default, all statistics are returned if the outputType specified is DwellMeanCenters (this is the default) or DwellConvexHulls.

Only the count is returned if the outputType specified is DwellFeatures or AllFeatures.

onStatisticField specifies the name of the fields in the target layer. statisticType is one of the following:

• Count—For numeric fields, this totals the number of values for all the points in each dwell. For string fields, this totals the number of strings for all the points in each dwell.
• Sum—Adds the total value of all the points in each dwell. This is for numeric fields.
• Mean—Calculates the average of all the points in each dwell. This is for numeric fields.
• Max—Calculates the largest value of all the points in each dwell. This is for numeric fields.
• Range—Finds the difference between the Min and Max values. This is for numeric fields.
• Stddev—Finds the standard deviation of all the points in each dwell. This is for numeric fields.
• Var—Finds the variance of all the points in each dwell. This is for numeric fields.
• Any—Returns a sample string of a point in each dwell. This is for string and numeric fields.
• First—Returns the first value of a specified field in the summarized track. This is for string and numeric fields. This parameters was introduced at ArcGIS Enterprise 10.8.1.
• Last—Returns the last value of a specified field in the summarized track. This is for string and numeric fields. This parameters was introduced at ArcGIS Enterprise 10.8.1.

//REST web examples
[{"statisticType": "Mean", "onStatisticField": "Annual_Sales"},{"statisticType": "Sum", "onStatisticField": "Annual_Sales"}]

//REST scripting example
"summaryFields": ["statisticType": "Mean", "onStatisticField": "Annual_Sales"},{"statisticType": "Sum", "onStatisticField": "Annual_Sales"}]

//Only return Count
"summaryFields": []

(Optional)

Determines which features are returned and the format. Four types are available:

• DwellMeanCenters—A point representing the centroid of each discovered dwell location. This is the default.
• DwellConvexHulls—Polygons representing the convex hull of each dwell group.
• DwellFeatures—All of the input point features determined to belong to a dwell are returned.
• AllFeatures—All of the input point features are returned.

//REST web example
DwellFeatures

//REST scripting example
"outputType": "DwellConvexHulls"

(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 1 day at a time. The time boundary parameter was introduced in ArcGIS Enterprise 10.8.1.

The timeBoundarySplit parameter defines the scale of the time boundary. In the case above, this would be 1. See the portal documentation for this tool to learn more.

REST scripting example: "timeBoundarySplit" : 1

REST web example: 2

//REST web example
1

//REST scripting example
"timeBoundarySplit": 2

(Required if timeBoundarySplit is specified)

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

Values: Milliseconds | Seconds | Minutes | Hours | Days | Weeks| Months | Years

//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

(Required)

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"

(Optional)

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