The Feature Layer (new) output in ArcGIS Velocity allows you to write output features to a new ArcGIS feature layer. When writing to this output type, either a spatiotemporal feature layer and map image layer or an ArcGIS Enterprise hosted feature layer is created. Once the layer or layers are created, they are available for use in Enterprise and your Enterprise organization, where they can be added to maps, applications, and more.
Feature layers created by Velocity have key differences from other 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.
- A data retention policy must be defined for deleting older data from the feature layer. Data retention options can be set to 1 hour, 1 day, 1 week, 1 month, 6 months, and 1 year. Any feature layer with data that grows over time requires a value be specified in the Data retention (time period for retaining data) parameter. For example, if the Data storage method parameter is set to Add all new features and each time the analytic is run, you enable the Keep existing features and schema option, you must set the data retention option.
- Older data can be exported to a feature layer archive before being deleted using the Data retention (time period for retaining data) parameter. Data exported to the feature layer archive is maintained for one year from the date of the export. To ensure data is exported to the feature layer archive, choose the Keep existing features and schema option every time the analytic runs. Specify the data retention options, and ensure that you choose the Export data option under Data export (feature layer archive).
Examples
Les exemples suivants illustrent des cas d’utilisation de la sortie :
- 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.
- 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 the features as identified by the track ID in a new feature layer.
Usage notes
Gardez les points suivants à l’esprit lorsque vous utilisez la sortie :
- 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.
- A data retention strategy must be specified in the Data retention (time period for retaining data) parameter. The Data retention (time period for retaining data) and Data export (feature layer archive) parameters do not apply if you enable the Replace existing features and schema option each time the analytic is run.
- If the Data storage method parameter is set to Keep only latest feature for each Track ID value, a track observation that is updated only has the editor user and date updated after the first observation.
Remarque :
Le nom de la couche d’entités spatio-temporelle doit être unique dans une organisation.
Dans Velocity, le nom de la couche d’entités spatio-temporelle doit être différent des noms du flux et de la couche en mode continu. En cas de doublon, il est impossible de créer une analyse temps réel dans Velocity. Ceci ne concerne que les couches d’entités Velocity en sortie. Cela ne s’applique pas aux couches d’entités hébergées sur ArcGIS Enterprise.
Parameters
Les paramètres de la sortie sont les suivants :
| Parameter | Description | Data type |
|---|---|---|
| Feature layer name | The name of the new feature layer. | Chaîne |
| Store data in spatiotemporal feature layer | Après avoir configuré les paramètres de connexion à la source, définissez la structure et les paramètres clés. If this parameter is unchecked (false), data will be written to a hosted feature layer in your organization. | Booléen |
| Data storage method | Spécifie si toutes les nouvelles entités sont ajoutées à la couche d’entités ou si les entités existantes sont mises à jour. Les options sont notamment les suivantes :
Remarque :If Keep only latest feature for each Track ID value is chosen, the value is true. | Booléen |
| Each time the analytic runs | Specifies how existing data in the feature layer is dealt with each time the analytic is started. Options are as follows:
Remarque :If Replace existing features and schema is chosen, the value is true. | Booléen |
| Aggregation styles | Specifies the bin styles for dynamic aggregation of the data. The bin styles are populated by default and can be modified. Bin styles can be defined for more spatial references or projections. Ce paramètre n'est applicable que si des données sont stockées dans une couche d'entités spatio-temporelle. | Geohashes |
| Editor tracking | Editor tracking sets the username and date when feature records are created or updated in the output feature layer. Check the Editor tracking check box on the output feature layer. Checking this parameter appends the created_date, created_user, last_edited_date, and last_edited_user fields to the feature layer schema. Ce paramètre n'est applicable que si des données sont stockées dans une couche d'entités spatio-temporelle. | Booléen |
| 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. Ce paramètre n'est applicable que si des données sont stockées dans une couche d'entités spatio-temporelle. | Chaîne |
| Feature Service Portal Item ID | ID d’élément du portail de l’élément de couche d’entités correspondant créé dans Enterprise. Ce paramètre ne s’affiche pas lorsque vous configurez la sortie, et ne peut être ni renseigné ni modifié. Il est renseigné automatiquement par ArcGIS Velocity. | Chaîne |
| Map Service Portal Item ID | The portal item ID of the corresponding map layer item created in Enterprise. Ce paramètre n'est applicable que si des données sont stockées dans une couche d'entités spatio-temporelle. | Chaîne |
| 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. The options are as follows: 1 hour 1 day, 1 week, 1 month, 6 months, and 1 year. Ce paramètre n'est applicable que si des données sont stockées dans une couche d'entités spatio-temporelle. | Chaîne |
| Data export (feature layer archive) | Specifies whether purged data is exported to a feature layer archive before being purged. The options are as follows: Do not export data and Export data. Data exported to the feature layer archive is maintained for one year from the date of the export. The Data retention (time period for retaining data) parameter does not apply if the Replace existing features and schema option is chosen. Ce paramètre n'est applicable que si des données sont stockées dans une couche d'entités spatio-temporelle. | Chaîne |
| Additional logging (optional) | Specifies whether logging for raw requests issued by Velocity is turned on. The default is False. Remarque :Only turn on this parameter for troubleshooting purposes and turn it off when troubleshooting is complete. Contact Esri Technical Support for help with troubleshooting. | Booléen |
Considerations and limitations
Tenez compte des points suivants lorsque vous utilisez la sortie :
- 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 should maintain a consistent schema.
- The feature layer (and map image layer) portal items associated with the Feature Layer (new) output must be owned by the creator 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 the Store data in spatiotemporal feature layer parameter is checked, a hosted feature layer is created in the Velocity spatiotemporal data store. Feature layers hosted by Velocity cannot be shared publicly.
When a feature layer is not hosted in a spatiotemporal data store
If the Store data in spatiotemporal feature layer parameter is unchecked, a hosted feature layer is created in ArcGIS Online. Consider the following when using this output:
- If you choose the Replace existing features and schema option, each time the analytic runs, the existing feature layer is replaced. If the feature layer has associated hosted feature layer views, the analytic returns an error message in the logs. All associated views must be deleted and removed from the recycle bin before restarting the analytic.
- Hosted feature layer outputs in ArcGIS Online consume credits for storage.
Vous avez un commentaire à formuler concernant cette rubrique ?