ArcGIS Velocity can be used to create analytic pipelines that perform either real-time or big data analytics on event data. The Velocity application provides options for creating, configuring, saving, and viewing analytics.
Create an analytic
In the Velocity application, the menu on the left contains an ANALYSIS section with options for creating real-time and big data analyses. Use either of these options to open the Real-Time Analytics or Big Data Analytics pages where new analytics can be created by clicking Create Analytic.
When creating a real-time analytic, you will choose an existing feed or create a new feed. When creating a big data analytic, you will define a data source for the big data analytic.
Once the feed or data source is chosen or created, you will begin configuring the analytic in the analytic editor. Use the analytic editor to configure tools, outputs, and additional data sources. Analytics can be saved, started, or further edited. Big data analytics can also be scheduled to run on a recurring basis.
Save an analytic
Once the analytic editor opens, to persist an analytic configuration click Create Analytic and provide a name and optionally a description.
After creating the analytic, you can continue to configure additional feeds, sources, tools, and outputs. As changes are made, the analytic can saved by clicking Save in the top right of the application. Analytics must have at least on input and one output before they can be started.
Toggle view type
Once an analytic is created and saved, additional options and controls are available, including the ability to toggle the view type. Analytics can be edited in either the workflow or model view, switching between the views is easily done in the application.
The workflow view offers a streamlined configuration experience to configure an analytic that references a single feed or source, processes the data in a sequence of one or more tools, and sends the resulting features to one or more outputs. The workflow view is ideal for simpler analytics with a single pipeline of processing.
Tools and outputs can be added to the analytic from the search bar or from the tool folders.
Tools can be dragged above or below each other to reorder the processing steps in an analytic.
Cards representing feeds, sources, tools, and outputs can be expanded allowing you to view and configure settings. The key fields are visible on the left of each card so you know the schema of the data at each step in the processing pipeline.
Workflow view can only be utilized when using a single pipeline analytic. If your analytic is complex (has more than one processing path for data) or invalid due to disconnected nodes, the toggle button to switch to workflow view will be inactive.
The model view offers a conventional node and port connection experience, similar to the service designer in ArcGIS GeoEvent Server or ModelBuilder in ArcGIS Desktop. Feeds or sources have a green background, analytics have a white background, and outputs have a blue background.
To connect different nodes such as a data source to a tool, a tool to another tool, or a tool to an output, click the output port of a node and hold and drag the cursor to connect to the input port of another node.
Model view is useful for configuring more complex analytics with multiple pipelines of processing.
An analytic can have multiple feeds, data sources, tools, and outputs. These elements can be configured in an analytic as a single pipeline or multiple pipelines. A pipeline defines the flow of event data from a feed or data source to any number of tools and then to any number of outputs.
Single pipeline analytic
A single pipeline analytic has a single processing path. This path can be as simple as one feed and one output or have many tools in the pipeline, including tools that leverage additional data sources and one or more outputs.
The workflow view is available only with single pipeline analytics. When more than one pipeline exists, the analytic is considered complex and can only be viewed in the model view.
Multiple pipeline analytic
A multiple pipeline analytic has more than one processing path for the event data.