Skip to main content
Tags in FLOW
DataFromSky avatar
Written by DataFromSky
Updated over 3 weeks ago

FLOW is a real-time monitoring solution that enables users to track, analyze, and interpret video data streams. However, categorizing and retrieving data efficiently has been a challenge, often leading to inconsistencies and errors. To address this, FLOW introduces Tags, a feature that allows users to assign meaningful identifiers to your data presented by widgets. Previously, data identification relied solely on a numerical ID, which could lead to confusion. Now, users can define and apply tags in a structured way, ensuring clarity across analytics setups. This improvement significantly enhances workflow efficiency by reducing ambiguity in data outputs and providing a unified labelling approach.

Tags Section

A dedicated Tags section is now available in FLOW, where users can access the default tag list and customize it to fit their needs.

Each tag consists of:

  • Icon

Visual descriptor of the Tag type in the UI. Users can enhance their workflow by assigning custom icons to better visualize their analytics types and maintain consistency in categorization. Recommended size: 64x64 pixels.

  • Tag Name

A descriptive label for easy reference.

  • Data Name

A unique identifier to maintain consistency. It is important to keep this property unique across other tags. It is also recommended to keep it unique across devices to make it easy to migrate.

Data Names should be unique across devices.

Default Tag List

FLOW provides a predefined set of tags for the most common scenarios, including:

  • bv (Blocking Vehicle)

May be used to identify a vehicle obstructing traffic flow, such as a parked car in a restricted area or a stalled vehicle in a lane.

  • ip (Illegal Presence)

May be used for objects or individuals present in unauthorized or restricted areas, such as pedestrians on highways or vehicles in no-entry zones.

  • lc (Lane Compliance)

May be used for monitoring vehicles staying within their designated lanes, helping to detect invalid lane departures or improper lane changes.

  • nm (Near Miss)

May be used for monitoring situations where two objects, such as vehicles or pedestrians, come dangerously close to colliding for various reasons.

  • pc (Pedestrian in Crossroad)

May be used for monitoring situations with pedestrians outside crosswalks or other dangerous road areas.

  • rl (Red Light Runner)

May be used for monitoring vehicles that fail to stop at red traffic lights.

  • ro (Road Obstacle)

May be used for monitoring objects that obstruct roadways, including debris, fallen branches and other objects.

  • sv (Speeding)

May be used for monitoring vehicles exceeding the speed limit.

  • tv (Turning Movement)

May be used for tracking vehicles making turns at intersections or roundabouts.

  • ww (Wrong Way)

May be used for monitoring vehicles travelling in the wrong direction on roads, highways, or one-way streets.

Using Tags in the UI

All types of widgets now include a Tag dropdown field in their Settings, allowing users to assign a tag to the widget. Only one tag per widget can be assigned.

Once assigned, widgets displayed in the Dashboard section will reflect the configured icon and name, improving data visibility and usability.

Exporting and Importing Tags

FLOW allows users to export and import BLOCK configuration settings navigating to Block -> Settings export and import. Tags settings are now included in this transfer. This allows moving Tags configuration between devices, which is particularly useful in scenarios where users need to maintain the same tagging structure across multiple installations.

Example: Tags in Data Output

Widgets can be read through Webhooks or REST API. Usually, a numeric widget ID would identify it. Using tags instead, specifically the Data Name record, helps the engineer set up valid communication to read the widget data. Below is an example of how a tag appears in a data record. Notice the final entry under “tags”, where the value “bv” (representing “Blocking Vehicle”) has been assigned as the Data Name for this tag type.

{
"analytic_id": 0,
"block_name": "embedded_micro - 13f07",
"cube_id": 11,
"data": {
"data_validity": "ok",
"evaluation_validity": "ok",
"object_count": 6,
"value": 6
},
"data_end_timestamp": "1738576610433",
"data_start_timestamp": "1738576610066",
"id": 4,
"name": "BV now",
"operator_attribute": "object_count",
"output_type": "widget",
"output_value_type": "value",
"tags": [
"bv"
]
}

Note: Although Tags are represented as an array, the ”tags” field can contain only a single tag per entry.

Conclusion

The introduction of Tags in FLOW provides a structured and efficient way to categorize and retrieve data across various analytics setups. By implementing a standardized approach, users can ensure consistency across devices while reducing errors in data interpretation. The ability to customize tags, assign icons, and seamlessly export/import them further improves the flexibility and usability of this feature. Whether tracking traffic misbehavior, analyzing movement patterns, or detecting safety risks, Tags enhance clarity and streamline data processing, making FLOW an even more powerful tool for real-time monitoring.

Did this answer your question?