Feature Layer (new)
The Feature Layer (new) output in ArcGIS Velocity allows you to write output features to a new ArcGIS feature layer. When you write to this output type, ArcGIS Velocity creates either a spatiotemporal feature layer and map image layer or an ArcGIS Enterprise hosted feature layer. After creation, you can add the layer or layers to maps and apps in your ArcGIS Enterprise organization.
Feature layers created by Velocity have key differences from other ArcGIS Enterprise hosted feature layers, including the following:
The associated data is stored in a spatiotemporal feature layer. As a result, the corresponding map image layer provides dynamic rendering and on-the-fly aggregation.
You must define a data retention policy to delete older data from the feature layer. You can set the data retention options to 1 hour, 1 day, 1 week, 1 month, 6 months, or 1 year. You must specify a value in the Data retention (time period for retaining data) parameter for any feature layer whose data grows over time. For example, if the Data storage method parameter is set to Add all new features and you enable the Keep existing features and schema option each time the analytic runs, you must set the data retention option.
Examples
The following are example use cases for the output:
After ingesting event data from IoT sensors using a feed and processing it in a real-time analytic, you want to store the features in a new feature layer.
You have configured a feed in 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.
You monitor environmental stations that each have an air quality sensor and a weather sensor reporting at different times, and you want a new feature layer that stores the latest state of each station. One pipeline carries the full station schema, and separate pipelines carry only the air quality or weather readings. All pipelines connect to the same output, so an update from one sensor changes only that sensor’s fields and keeps the latest values from the other sensor.
Usage notes
Note the following when working with the output:
If you enable the Keep existing features and schema option each time the analytic is run, the features written to the new output feature layer must maintain a consistent schema.
The new feature layer and map image layer created by the output do not appear until the analytic is started and has successfully generated the output.
You must specify a data retention strategy in the Data retention (time period for retaining data) parameter. The Data retention (time period for retaining data) option does not apply if you enable the Replace existing features and schema option each time the analytic runs.
If the Data storage method parameter is set to Keep only latest feature for each Track ID value, Velocity updates only the editor user and date for a track observation after the first observation.
When the Data storage method parameter is set to Keep only latest feature for each Track ID value, choose the Keep the newer feature for a Track ID based on Start Time option in the Advanced options section. Velocity then compares the time specified in the Start Time option of each incoming feature to the stored feature for that track ID and skips the write if the incoming feature is older. This preserves the latest observation when events arrive out of order (for example, from multiple sources or Kafka).
This parameter requires a
START_TIMEfield. If none is defined, a validation warning appears and each incoming feature is treated as new. This applies only to spatiotemporal feature layers.
Note:
The spatiotemporal feature layer name must be unique within an organization.
In Velocity, the spatiotemporal feature layer name must be different from the feed and stream layer names. If there is a duplicate name, you cannot create a real-time analytic in Velocity. This only applies to Velocity feature layer outputs; it does not apply to ArcGIS Enterprise hosted feature layers.
- The Simplify feature geometry parameter is only available when the Store data in spatiotemporal feature layer parameter is turned on. If your feature geometries are already simple, you can leave this parameter off to improve write performance.
Parameters
The following table describes the parameters for the output:
|
Parameter |
Description |
Data type |
|---|---|---|
|
Feature layer name |
The name of the new feature layer. |
String |
|
Store data in spatiotemporal feature layer |
After configuring source connection parameters, define the schema and the key parameters. If you do not check this parameter, data is written to a hosted feature layer in your organization. |
Boolean |
|
Data storage method |
Specifies whether all new features are added to the feature layer or existing features are updated. Options include the following:
Note:If Keep only latest feature for each Track ID value is chosen, this value is |
Boolean |
|
Keep the newer feature for a Track ID based on Start Time |
This parameter is available in the Advanced options section when the Data storage method parameter is set to Keep only latest feature for each Track ID value. When this parameter is set to Yes with the Track ID and Start Time options specified, Velocity keeps the newer feature per track ID and skips writes for older incoming features. When this parameter is set to No (default), incoming features overwrite the stored feature for a track ID as they arrive. This parameter requires a This parameter is only applicable when data is stored in a spatiotemporal feature layer. |
Boolean |
|
Each time the analytic runs |
Specifies how existing data in the feature layer is handled each time the analytic starts. Options include the following:
Note:If Replace existing features and schema is chosen, this value is |
Boolean |
|
Aggregation styles |
Specifies bin styles for dynamic aggregation of the data. The default bin styles are populated automatically, and you can modify them. You can also define bin styles for more spatial references or projections. This parameter is only applicable when data is stored in a spatiotemporal feature layer. |
Geohashes |
|
Simplify feature geometry |
Simplifies feature geometries to ensure that Velocity writes them to the database correctly. If you know the feature geometries are already simple, you can leave this parameter turned off to improve write performance. This parameter is available in the Geometry options section. This parameter is only applicable when the Store data in spatiotemporal feature layer parameter is turned on. |
Boolean |
|
Editor tracking |
Editor tracking sets the username and date when feature records are created or updated in the output feature layer. Turn on the Enable editor tracking option on the output feature layer. If you turn this parameter on, it appends the This parameter is only applicable when data is stored in a spatiotemporal feature layer. |
Boolean |
|
Creator and editor username |
Specifies the creator or editor username 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 and editor username parameter does not apply if the Editor tracking parameter has been turned off. This parameter is only applicable when data is stored in a spatiotemporal feature layer. |
String |
|
Feature Service Portal Item ID |
The portal item ID of the corresponding feature layer item created in ArcGIS Enterprise. This parameter is not displayed when configuring the output and cannot be populated or modified. It is automatically populated by ArcGIS Velocity. |
String |
|
Map Service Portal Item ID |
The portal item ID of the corresponding map layer item created in ArcGIS Enterprise. This parameter is only applicable when data is stored in a spatiotemporal feature layer. |
String |
|
Data retention (time period for retaining data) |
Specifies the data retention strategy, or time period after which older data is deleted from the feature layer. Options include the following: 1 hour, 1 day, 1 week, 1 month, 6 months, and 1 year. This parameter is only applicable when data is stored in a spatiotemporal feature layer. |
String |
|
Additional logging (optional) |
Specifies whether logging for raw requests issued by Velocity is turned on. The default is False. Note:Only turn on this parameter for troubleshooting purposes and turn it off when troubleshooting is complete. Contact Esri Technical Support for help with troubleshooting. |
Boolean |
Considerations and limitations
Consider the following when using the output:
If you choose the Keep existing features and schema option, each time the analytic is run, the features written to the new output feature layer must maintain a consistent schema.
The creator must own the feature layer and map image layer portal items associated with the Feature Layer (new) output for Velocity to write to the output. To change ownership of an item, reconfigure the analytic to write to an existing feature layer using the Feature Layer (existing) output.
When a feature layer is hosted in a spatiotemporal data store
If you check the Store data in spatiotemporal feature layer parameter, Velocity creates a hosted feature layer in the ArcGIS Data Store spatiotemporal big data store. You cannot share these layers publicly.
When a feature layer is not hosted in a spatiotemporal data store
If you do not check the Store data in spatiotemporal feature layer parameter, ArcGIS Enterprise creates a hosted feature layer. Consider the following when using this output:
- If you choose the Replace existing features and schema option, Velocity replaces the existing feature layer each time the analytic runs. If the feature layer has associated hosted feature layer views, the logs contain an error message. Delete all associated views and remove them from the recycle bin before restarting the analytic.