Introduction to outputs

An output in ArcGIS Velocity is a result or action to be taken as the final step in a real-time analytic. Analytics can emit data to a variety of destinations, including storing data to a feature layer, sending an email, writing to a cloud store, and pushing to a third-party system for device actuation. A real-time analytic must have at least one output and can send data to multiple outputs at the same time.

Examples

The following are examples of using outputs:

• An analyst creates a feature layer to store sensor observations after being processed in a real-time analytic.

• An email with a relevant message and information should be sent from a real-time analytic if a feature meets a certain criteria.

Outputs in real-time analytics

Real-time analytics process data being collected through a feed and analyze each message as it is received. After processing is complete in the analytic, each feature is sent to an output individually. It is important to consider this when configuring certain outputs.

For example, if you're configuring an Email output, a new email is sent for each feature sent to that output. For high-velocity feeds, this may not be the appropriate behavior. As a best practice, use the Email output only for outputs that are expected to occur occasionally.

The following output types are available in real-time analytics:

• ArcGIS

  • Feature Layer (new)

  • Feature Layer (existing)

  • Stream Layer

• Cloud

  • Azure Event Hub

  • Azure IoT Hub

  • Amazon SNS

  • Amazon SQS

  • AWS IOT

• Web and messaging

  • Email

  • Text Message

  • HTTP

  • Kafka

  • RabbitMQ

  • Slack

  • TCP (Client)

  • Microsoft Teams

  • UDP (Client)

  • Write to Local File

• Integrations

  • Trimble Unity Maintain