Feature Layer (new)

The Feature Layer (new) output allows you to write output features to a new ArcGIS feature layer. When writing to this output type, a feature layer and a corresponding map image layer will be created. Once created, this feature layer and map image layer will be available for use in ArcGIS Velocity and your ArcGIS Online organization where it can be added to maps, applications, and more.

Feature layers created by Velocity have some key differences from other ArcGIS Online hosted feature layers including:

  • The associated data is stored in the spatiotemporal big data store. As a result, the map image layer provides dynamic rendering and on-the-fly aggregation.
  • A data retention policy must defined for when older data will be purged from the feature layer. Data retention options include: No Purge, One Day, One Week, One Month, Six Months, and One Year. Any feature layer with data that grows over time (for example, if the Data Storage Method is set to Add New Features and each time the analytic is run you Keep existing features and schema) requires a Data Retention Strategy other than No Purge. For more information, see About data retention.
  • Older data can be exported to a feature layer archive (cold store) prior to being purged using the Data Retention Export Strategy parameter. Data exported to the feature layer archive (cold store) is maintained for one year from the date of the export. The Data Retention Export Strategy parameter does not apply if the Data Retention Strategy parameter is set to No Purge.

Example

  • After ingesting event data from IoT sensors in a feed and a real-time analytic, you want to store the features in a new feature layer.
  • After performing analysis in a big data analytic, you want to write the resulting analysis features to a new feature layer.
  • You have configured a feed within a real-time analytic to process events as they occur. You only want to store the latest state of your features as identified by the Track ID in a new feature layer.

Usage notes

  • If you choose Keep existing features and schema each time the analytic is run, the features written to the new output feature layer should maintain a consistent schema.
  • The new feature layer and map image layer created by the output will not appear until the analytic is started and has successfully generated the output.
  • A data retention strategy must be specified in the Data Retention Strategy parameter. If you choose to Replace existing features and schema each time the analytic is run, the strategy is automatically set to No Purge.
  • When Editor tracking is enabled and the Data Storage Method is set to Add new features, the creator and editor user and date will always be the same. If the Data Storage Method is set to Keep latest feature, a track observation that is updated will only have the editor user and date updated after the first observation.

Parameters

ParameterDescriptionData Type

Name

The name of the new feature layer.

String

Data Storage Method

Specifies whether all new features are added to the feature layer or if existing features are updated. Options include:

  • Add New Features—All new features will be added to the feature layer.
  • Keep Latest Feature—Only the latest feature for each unique Track ID will be kept. If selected, the output data schema should have a Track ID and Start Time key fields identified.

Boolean

Note:

If Keep Latest Feature is selected, the value is true.

Each time the analytic is run

Specifies how existing data in the feature layer is dealt with each time the analytic is started. Options include:

  • Replace existing features and schema—Each time the analytic is started, the features and schema present in the feature layer are discarded and new features and schema are written.
  • Keep existing features and schema—Each time the real-time analytic is started, existing features and schema are maintained. The new feature is appended to the existing data.

Boolean

Note:

If Replace existing features and schema is selected, the value is true.

Aggregation Styles

Specifies the bin styles to enable for dynamic aggregation of the data. The bin styles are populated by default and can be modified. Bin styles can be defined for additional spatial references or projections.

Geohashes

Editor tracking

Enables editor tracking on the output feature layer. Editor tracking sets the username and date when feature records are created or updated in the output feature layer.

Enabling this parameter will append a created_date, created_user, last_edited_date, and last_edited_user field to the feature layer schema.

Boolean

Creator or editor username

Specifies the username to use as the creator or editor for processed data. The username can be derived from a field of the incoming data or set as the username of the analytic owner.

The Creator or editor username parameter does not apply if the Editor tracking parameter has been disabled.

For details, see Usage notes.

String

Feature Service Portal Item ID

The Portal Item ID of the corresponding feature layer item created in ArcGIS Online.

This parameter is not displayed when configuring the output and cannot be populated or modified. It is automatically populated and updated as needed.

String

Map Service Portal Item ID

The Portal Item ID of the corresponding map layer item created in ArcGIS Online.

This parameter is not displayed when configuring the output and cannot be populated or modified. It is automatically populated and updated as needed.

String

Data Retention Strategy

Specifies the data retention strategy, or time period after which older data will be purged from the feature layer.

Options include: No Purge, One Day, One Week, One Month, Six Months, and One Year.

For details, see the Usage notes above.

String

Data Retention Export Strategy

Specifies whether purged data is exported to a feature layer archive (cold store) prior to being purged. Options include: Do not export data and Export data.

Data exported to the feature layer archive (cold store) is maintained for one year from the date of the export. The Data Retention Export Strategy parameter does not apply if the Data Retention Strategy parameter is set to No Purge.

String

Considerations and limitations

  • If you select to Keep existing features and schema each time the analytic is run, the features written to the new output feature layer should maintain a consistent schema.