Metadata and reporting requirements for images and videos not reported as part of other studies¶
1. Introduction¶
Purpose¶
This document outlines metadata requirements and technical specifications for images and videos not covered as partial deliveries from other surveys. The goal is to ensure alignment with Equinor requirements and Data Delivery Standards. These standards aim to facilitate robust environmental accounting and reporting, particularly concerning images and videos.
Scope¶
This document covers the technical, operational, and reporting requirements for images and videos, including:
-
Metadata fields required for survey documentation.
-
If relevant, sensor configurations and technical specifications for mobile sensor platforms.
-
File formats and data delivery standards for images, videos, and geospatial data.
-
Reporting requirements for integrating survey results into external databases like GBIF (Global Biodiversity Information Facility) and NEA (Norwegian Environment Agency’s database).
The scope ensures alignment with international and regional regulations while providing flexibility to accommodate project-specific needs.
Nomenclature for biology shall be reported in accordance with Catalogue of Life, and, if relevant, documentation of pollution and habitat shall be reported in accordance with e.g. habitat classification. Also, other country specific requirements might be relevant.
Target Audience¶
The intended audience for this document includes external:
Vendors: Such as Survey providers tasked with data collection and delivery.
Marine Biologists and Ecologists: Professionals responsible for classifying species and habitats based on survey data.
Data technical teams Data technical teams to implement the data validation according to the standards defined.
Document Structure¶
To facilitate ease of use and navigation, the document is organized into the following sections:
Metadata Requirements:
Details metadata fields necessary for survey documentation, including survey-specific and geospatial metadata.
Data Formats and Delivery:
Specifies file formats, naming conventions, and standards for delivering survey outputs.
Integration and Reporting:
Explains how data should be reported and integrated into external databases, including templates and examples.
Quality Assurance:
Defines validation and review processes to ensure data accuracy and consistency.
Glossary:
Includes definitions of key terms and acronyms used throughout the document.
2. Meta data requirements¶
2.1 Overview¶
Metadata plays a pivotal role in ensuring the consistency, traceability, and usability of images and video data. It serves as the backbone for data integration, regulatory compliance, and effective environmental analysis. This section outlines the core metadata categories necessary to support these objectives and explains their importance.
The metadata requirements are grouped into the following categories
I. Survey-Specific Metadata:
Captures details about the survey’s context, including project associations, event IDs, and survey dates. This metadata ensures traceability and enables the aggregation of related datasets across campaigns.
II. Geospatial Metadata:
Provides precise geographical coordinates and geodetic details for surveyed locations, enabling accurate mapping and spatial analysis critical for environmental reporting and habitat classification.
III. Sensor Metadata: Documents the technical details of sensors and equipment used during the survey, such as sensor types, operational parameters, and data resolution. This metadata is essential for understanding the conditions under which the data was captured and ensuring it meets technical and quality standards.
Each of these metadata categories is designed to facilitate seamless integration with regulatory requirements and databases such as GBIF (Global Biodiversity Information Facility). They also ensure that survey outputs align with global environmental and scientific standards, supporting robust environmental management and decision-making processes.
In the subsequent sections, each metadata category is detailed with specific field descriptions, formats, and validation requirements to provide a comprehensive framework for documenting and delivering seabed survey data.
2.2 Survey-Specific Metadata¶
Survey-specific metadata defines the operational context of a survey, ensuring data traceability and enabling aggregation across related datasets.
-
Purpose:
- To link survey data to its broader campaign or project.
- To maintain a clear record of survey-specific attributes for reporting and compliance.
-
Key Fields:
-
Project/Asset Name: Links the survey to a specific project or operational asset.
-
Location ID: Identifies the survey station or area.
-
Survey Date: Specifies the date of the survey activity.
-
Format Guidelines:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Project/Asset Name | Text | Unique identifier for campaign link | Oseberg H |
| Location ID | Text | Identifier for survey location | Camera 160 |
| Survey Date | Date (YYYY-MM-DD) |
Date of survey activity | 2024-01-15 |
-
Validation:
-
Ensure unique IDs for Parent Event, Location, and Event fields.
-
Cross-reference survey metadata with operational records.
-
2.3 Geospatial Metadata¶
Geospatial metadata provides precise locational data critical for mapping and analysing surveyed areas.
-
Purpose:
- To ensure spatial accuracy and facilitate geospatial analyses for habitat classification and environmental reporting.
-
Key Fields:
-
Latitude and Longitude: Coordinates in decimal degrees.
-
Geodetic Datum: Specifies the geodetic system (e.g., WGS84(EPSG4326)).
-
Country Code: ISO 3166-1 alpha-2 format.
-
Survey Center elevation: Average depth (water or soil) or height above sea level of the survey area.
-
Format Guidelines:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Latitude | Decimal (8 digits) | Latitude in decimal degrees | 59.12345612 |
| Longitude | Decimal (8 digits) | Longitude in decimal degrees | 10.65432123 |
| Geodetic Datum | Text | Geodetic reference system | WGS84(EPSG4326) |
| Country Code | Text | Country code of location | NO |
| Survey Center elevation | Decimal (2 digits) | Average elevation of surveyed area in meters | 200.45 |
-
Validation:
-
Ensure all coordinates fall within the operational survey area.
-
Verify datum consistency across all survey records.
-
Original coordinates, as measured or data source should be retained or archived.
Any coordinate transformations applied to coordinate data should, when possible, be applied to the original coordinates, rather than coordinates that have been transformed at an earlier stage in the data lifecycle.
2.4 Sensor Metadata¶
Sensor metadata describes the equipment used during the survey, ensuring transparency and reproducibility of data collection.
-
Purpose:
-
To document the specifications and performance of sensors used for data capture.
-
To validate that data is collected under appropriate technical conditions.
-
-
Key Fields:
-
Sensor Type: E.g., Digital Camera.
-
Sensor Carrier: Platform carrying the sensor (e.g.,camera stand, ROV, Vessel).
-
Altitude: Operational altitude for imaging sensors (above sea level or seabed).
-
Operational Parameters: Pitch, roll, and heading of sensors.
-
Format Guidelines:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Sensor Type | Text | Type of sensor used | Digital Camera |
| Sensor Carrier | Text | Platform carrying the sensor | ROV |
| Altitude* | Decimal (1-2) | Operational altitude (meters) | 2.5 |
| Pitch* | Decimal | Sensor pitch (degrees) | -1.2 |
| Roll* | Decimal | Sensor roll (degrees) | 0.5 |
| Heading* | Decimal | Sensor heading (degrees) | 180.0 |
*If relevant (mobile sensor carrier)
Metadata Field Descriptions:
This table defines the required fields for sensor metadata, including spatial and operational parameters.
| Field name | Format | Description |
|---|---|---|
| Date* | Text 10 characters | YYYY-MM-DD (2022-06-31) |
| Time* | Text 12 characters | HH:MM:SS.SSS (06:32:04.261) |
| UTM Easting | Floating number, 2 decimals | If relevant, Horizontal Position (x) Reference point on Sensor |
| UTM Northing | Floating number, 2 decimals | If relevant, Horizontal Position (y) Reference point on Sensor |
| Sensor Z | Floating number, 2 decimals | If relevant, Vertical Position (z) Reference point on Sensor DEPTH negative values HEIGHT as positive. All values in meters. |
| Roll | Floating number, 2 decimals | If relevant, Sensor roll (starboard down positive value) |
| Pitch | Floating number, 2 decimals | If relevant, Sensor pitch (bow up positive value) |
| Gyro | Floating number, 2 decimals | If relevant,Sensor heading (heading 360º) |
| Altitude | Floating number, 2 decimals | If relevant, SENSOR (reference point) distance above surface. Always positive values in meters |
| KP | Floating number, 5 decimals | If relevant, Kilometres post in km. |
| Number of cameras | Integer number | From 1 to n |
| Video name | Text 30 characters | SurveyID_timestamp (EQ22900 _ 2020010322594066) |
| Time form start* | Text 12 characters | HH:MM:SS.SSS (00:00:00.047) |
*Date/Time = ISO 8601 format
-
Validation:
-
Validate sensor data against operational requirements (e.g., altitude and heading accuracy).
-
Ensure metadata overlays (e.g., timestamp, location) in video and image files.
-
2.5 Metadata Validation and Integration¶
-
Purpose:
-
To ensure the integrity and consistency of metadata across all survey records.
-
To facilitate integration with regulatory databases and environmental systems.
-
-
Guidelines:
-
Metadata should be validated using predefined schemas or templates.
-
Standardized file naming conventions must be applied to ensure seamless integration.
-
3. Data Formats and Delivery¶
3.1 Overview¶
This section outlines the standardized data formats, file naming conventions, and delivery protocols for seabed fauna surveys. These requirements ensure consistency, traceability, and seamless integration with regulatory bodies or databases such as GBIF. Specifications include file formats for videos, images, and associated metadata, along with guidelines for organizing and delivering the data.
The section is divided into the following subsections:
I. File formats:
Describes the recommended file formats and their associated metadata
II. File naming conventions:
Defines how the data is named
III. Delivery protocols:
Defines what, how and where the data are to be delivered
3.2 File Formats¶
The individual datatypes are to be delivered on the following formats:
-
Video Files:
-
Format: H264 (MPEG-4 AVC), minimum resolution of 720p
-
Metadata Overlay, if relevant: Date, time, geospatial coordinates (latitude/longitude), depth, altitude, and camera orientation (pitch, roll, heading)
-
Maximum File Length: 15 minutes.
-
-
Still Images:
-
Format: PNG or JPG with high resolution
-
Metadata: Timestamp, geospatial coordinates, and camera orientation
-
-
Track Data, if relevant:
-
Format: ASCII comma-separated files (.VTF)
-
Fields: Include timestamp, latitude, longitude, depth, pitch, roll, and heading.
-
3.3 File Naming Conventions¶
The individual datatypes are to be delivered in accordance with the following file naming conventions:
-
Videos: < SurveyID >< DateTime >< CameraName >.mp4
Example: EQ22900_20240101T120000_CAM1.mp4
-
Still Images: < SurveyID >< DateTime >< CameraName >.png
Example: EQ22900_20240101T120000_CAM1.png
-
Track Files: < SurveyID >_VIDEO.VTF or < SurveyID >_STILL.VTF
Example: EQ22900_VIDEO.VTF
-
Folder structure: Files should be organized by survey date and time (e.g., 20240101_12 )
3.4 Delivery protocols¶
The individual datatypes are to be delivered in accordance with the following delivery protocols:
1. Data Package:
-
Include videos and/or still images, and if relevant track files and a survey report in PDF format
-
Compress data into a single package with a logical directory structure.
2. Geospatial Data:
- Deliver point and polygon data in geodatabase formats, referred in chapter 4 below.
3.Validation:
- Ensure all files comply with format specifications and metadata accuracy before delivery.
4. Delivery Location:
- Please refer to the Data delivery guidelines mentioned here: External User Guide - SSU Documentation - for external Vendors
4. Integration and Reporting¶
4.1 Reporting requirements¶
The following datatypes (DT1-DT2) are to be reported.
A presentation and/or a PDF file describing objective, methods, findings in a geospatial context shall follow the reported data.
If no country specific requirements are given, the following datatypes (DT1-DT2) are to be reported.
These tables are found here in the following Excel fill that is to be used for reporting:
GBIF Template
Info:Please fill out the template as is, do not remove/add sheets/Columns.
DT1: Sampling Events¶
| Field | Description | Example |
|---|---|---|
| parentEventID | An identifier for the broader Event that groups this and potentially other Events. E.g., plant name. | Hammerfest |
| locationID | An identifier for the set of location information. May be a global unique identifier or an identifier specific to the data set. | NFV1 |
| eventID | An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set. E.g., “prøvepunkt”. | F1 |
| eventStartDate (yyyy-mm-dd) |
The date-time when the start of the event was recorded. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). | 2024-09-26 |
| eventEndDate (yyyy-mm-dd) |
The date-time when the end of the event was recorded. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). | 2024-09-27 |
| samplingProtocol | The name of, reference to, or description of the method or protocol used during an Event. E.g., "Jord", "Luft", "Ferskvann", "Saltvann", "Sediment", "Vevsanalyse", "Artsanalyse", "Nedbør". | Jord |
| decimalLatitude | The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. | 41.0983423 |
| decimalLongitude | The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. | -121.1761111 |
| geodeticDatum | The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude are based. | EPSG:4326 |
| maximumElevationInMeters | The upper limit of the range of elevation in meters. | 14.863 |
| maximumDepthInMeters | The greater depth of a range of depth below the local surface, in meters. | 10 |
| countryCode | An identifier for the country where the event occurred. Recommended best practice is to use ISO 3166-1-alpha-2 country codes. | NO |
| datasetName | The name identifying the dataset from which the record was derived. E.g., report name and number. | APN 66140.01.2025 |
| sampleSizeValue | A numeric value for a measurement of the size (time duration, length, area, or volume) of a sample in a sampling event. A sampleSizeValue must have a corresponding sampleSizeUnit. | 1-1,9 |
| sampleSizeUnit | The unit of measurement of the size (time duration, length, area, or volume) of a sample in a sampling event. A sampleSizeUnit must have a corresponding sampleSizeValue. | Depth in meters |
| eventRemarks | Comments or notes about the event. E.g., sensor or standard used. | Langvannet, Kvaløya |
DT2: Associated Occurrences (Media)¶
| Field | Description | Example |
|---|---|---|
| eventID | An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set. E.g., “prøvepunkt”. | F1 |
| occurrenceID | An identifier for the Occurrence. | F1-1 |
| eventStartDate (yyyy-mm-dd) |
The date-time when the start of the event was recorded. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). | 2024-09-26 |
| eventEndDate (yyyy-mm-dd) |
The date-time when the end of the event was recorded. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). | 2024-09-27 |
| type | The nature or genre of the resource. In this case, the type of media. | E.g., image, video, etc. |
| decimalLatitude | The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. | 41.0983423 |
| decimalLongitude | The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. | -121.1761111 |
| associatedMedia | Name of (or link to) media file. | 20250401_Coral.jpg |
| occurrenceRemarks | Comments or notes about the occurrence. | Measurement below detection limit. |
5. Quality Assurance¶
5.1 Overview¶
Quality assurance ensures seabed fauna survey data is accurate, reliable, and meets regulatory standards.
5.2 QA During Data Collection¶
Sensor Checks:
- Calibrate sensors before and after surveys.
Standards:
- Keep sensors 1–3 meters above the seabed and ensure metadata (date, time, coordinates) is recorded.
Real-Time Monitoring:
- Check data quality during collection to fix any issues immediately.
5.3 QA During Data Processing¶
File Validation:
- Ensure all files are complete, accurate, and named correctly.
Cross-Checks:
- Match metadata with video and image content to confirm consistency.
5.4 QA for Reporting¶
Compliance:
- If the data does not meet requirements specified in this document, please notify the Equinor contact person specified in the contract.
- If the visual seabed biology data meets different requirements than those specified in this document, please ensure that all deliverables comply with that regulatory standards and indicate which standard has been followed
Completeness:
- Include all required files and reference them properly in the survey report.
6. Glossary¶
The following terms and acronyms are used in this document and are defined here for clarity.
| Acronym | Explanation |
|---|---|
| ASCII | American Standard Code for Information Interchange |
| AVC | Advanced Video Coding |
| DT | Data Type |
| GBIF | Global Biodiversity Information Facility |
| ID | Identification |
| JPG | Joint Photographic Experts Group |
| KP | Kilometer Post |
| MPEG-4 | Moving Pictures Expert Group 4 |
| NEA | Norwegian Environment Agency |
| Portable Document Format | |
| PNG | Portable Network Graphic |
| QA | Quality Assurance |
| ROV | Remotely Operated Vehicle |
| UTM | Universal Transverse Mercator |
| VTF | Video Track Format |
| WGS84(EPSG4326) | World Geodetic System 1984 |