📸 Video Snapshots

The Video Snapshots feature allows users to capture still images (snapshots) from both live and on-demand video streams. These snapshots are stored for future reference and analysis, with automatic metadata association based on the video source context.

🎞️ Snapshot Sources

Live Video

  • Snapshots can be captured from live video streams at any time.
  • They do not require active mission recording.
  • If recording is not active, snapshots are associated with the Platform only.
  • If recording is active, they are associated with Mission, Sensor, Platform

On-Demand Video

  • Users can also take snapshots from archived or recorded video playback.
  • These snapshots will always be associated with Mission, Sensor, Platform

In a multi-sensor scenario, the snapshot will apply to the currently selected player.

🎬 Taking snapshots

To take a snapshot, press the Snapshot button:

Snapshots

The Snapshot dialog box will open, capturing the current video frame:

Snapshots

⬇️ You can download the snapshot immediately, without creating or saving it as a document, by clicking the Download Snapshot button at the bottom of the dialog box.

Add a Title, Description, and Tag metadata. Assign User groups (from the list of available user groups).
If KLV metadata exists in the stream (or file), the current timestamp will be extracted and associated with the snapshot. For recorded videos, this means the timestamp will differ from the snapshot's creation time.

🏷️ User-Defined Tags

Users can create and manage their own tags to organize and categorize content more effectively. Tags are entered as free text, giving users complete flexibility to define labels that best suit their needs. When a new tag is created, it is automatically added to the list of existing tags, allowing users to reuse it later.

🔐 Access Control

Snapshots follow the same access control model as other documents:
- Admins & SuperAdmins: Full access
- GroupAdmins: Access and ability to mark as restricted
- Regular users: Access to non-restricted and group documents

📁 Snapshot Storage

Snapshots are treated as documents and saved into the same directory as document files

📄 Snapshot File Naming Convention

When a snapshot is taken, its filename is automatically generated using a structured format that ensures uniqueness and readability. The naming convention follows this pattern:

YYYY-MM-DD-HH:MM:SS-username_title.jpg

🔤 Format Details:

  • YYYY-MM-DD – Year, month, and day of the snapshot
  • HH:MM:SS – Hour, minute, and second of the snapshot (24-hour format)
  • username – The username of the person who captured the snapshot
  • title – The user-supplied title of the snapshot (spaces replaced with underscores)
  • .jpg – Snapshot is stored as a JPEG image

📌 Example:

If a user named jdoe captures a snapshot titled "Target Acquired" on March 27, 2025, at 14:05:09, the filename will be:

2025-03-27-14:05:09-jdoe_Target_Acquired.jpg

This format ensures:
- Easy sorting and identification
- Inclusion of author and context in the filename
- Compatibility with most filesystems

📑 Metadata Associated with Each Snapshot

Each snapshot is stored as a Document of type Image, and includes metadata:

Field Description
documentType Always set to Image
title User-supplied
description Optional text description
missionId Only if mission recording is active
sensorId Only if mission recording is active
platformName Always provided. Extracted automatically from the current configuration
tags Optional descriptive metadata.
timestamp Automatically set if the stream contains KLV metadata. Snapshot will also have a creation timestamp
fileName Snapshot image filename
thumbnail Auto-generated preview (a link to the actual snapshot). (jpeg)

✅ Best Practices

  • Use meaningful titles when saving snapshots.
  • Add relevant tags to simplify searching.