Skip to main content

Feature Layer (existing)

The Feature Layer (existing) output in ArcGIS Velocity allows you to write output features to an existing hosted feature layer (spatiotemporal), an existing ArcGIS Enterprise portal hosted feature layer, an existing ArcGIS Online organization hosted feature layer, or an existing ArcGIS Server site feature layer. Velocity writes features to an existing feature layer, as opposed to creating one.

Examples

The following are example use cases for the output:

  • After ingesting real-time features from IoT sensors through a feed and a real-time analytic, an asset manager wants to add those observations to an existing feature layer.

  • A business analyst ingests a set of existing historical observations from an external cloud store to configure a real-time analytic to process events as they occur and captures the new observations in an existing feature layer.

Usage notes

Keep the following in mind when working with the output:

  • The selected feature layer must be a hosted feature layer (spatiotemporal), an Enterprise portal hosted feature layer, an ArcGIS Online organization hosted feature layer, or an ArcGIS Server site hosted feature layer.

  • The schema of the incoming data and the destination feature layer must generally match. Each should have the same geometry type and spatial reference, and the fields present in the incoming data should exist in the destination feature layer. Differences can include the following:

    • The destination feature layer can have more fields not present in the incoming data that you can use for data enrichment.

    • The TRACK_ID and START_TIME tags in the incoming data schema do not have to match those in the destination feature layer when using ArcGIS Online or ArcGIS Server feature layers.

    • Use the Map Fields tool to transform the schema of the incoming data in an analytic workflow to align with the schema of the output feature layer.

  • When the incoming data schema does not have a TRACK_ID value set, you can write to a feature layer (existing) that does not have a track ID. Keep the following behavior in mind:

    • When writing with the Keep only latest feature for each Track ID value data storage method option, Velocity writes all incoming features to the target dataset.

  • ArcGIS Server feature layers must be referenced in an ArcGIS organization portal item ID. To do this, go to your ArcGIS organization content page, and add an item referencing the layer by URL. If applicable, store credentials with this ArcGIS organization item. You can then configure the hosted feature layer (spatiotemporal) existing output to point to this ArcGIS organization portal item ID.

  • For a hosted feature layer (spatiotemporal), a data retention policy is required for all output feature layers because data grows over time. When writing to an existing feature layer and using the Add all new features option in the Data storage method parameter, the selected feature layer must have a data retention policy configured.

    Learn more about data retention

  • If the Data storage method parameter is set to Keep only latest feature for each Track ID value, when Velocity updates a track observation, it updates the editor name, date, and time after the first observation.

Parameters

The following are the parameters for the output:

Parameter

Description

Data type

Feature Service Portal Item ID

The portal item ID of the corresponding feature layer item created in Enterprise.

The user creating the analytic must create the feature layer.

String

Data storage method

Data stored in a spatiotemporal feature layer supports high-velocity ingestion, high-volume storage over time, dynamic aggregation, and automated data retention if checked (true). This is the default.

  • Add all new features—Velocity adds all new features to the feature layer.

  • Keep only latest feature for each Track ID value—Velocity keeps only the latest feature for each unique track ID. The output data schema should have key fields identified for the Track ID and Start Time options.

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 analytic owner.

The Creator and editor username parameter only applies and is shown when the existing feature layer has editor tracking turned on.

Learn more about usage notes

String

Additional logging (optional)

Specifies whether Velocity enables logging for raw requests. The default is False.

Note:

Turn on this parameter only for troubleshooting, then turn it off when complete. Contact Esri Technical Support for help with troubleshooting.

Boolean