Metadata and reporting requirements for environmental sampling and point measurements¶
1. Introduction¶
Purpose¶
This document outlines metadata requirements and technical specifications for conducting environmental sampling and point measurements. 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 chemical sampling and identification of present biology.
Scope¶
This document covers the technical, operational, and reporting requirements for environmental sampling and point measurements, including:
-
Metadata fields required for survey documentation.
-
Sensor configurations and technical specifications for survey equipment.
-
File formats, including geospatial information for chemistry, geology and biology.
-
Reporting requirements
The scope ensures alignment with international and regional regulations while providing flexibility to accommodate project-specific needs.
Nomenclature for chemistry and biology shall be reported in accordance with IUPAC and Catalogue of Life respectively, and, if relevant, other country specific requirements.
Target Audience¶
The intended audience for this document includes external:
Vendors: Such as survey providers and laboratories tasked with data collection and/or delivery.
Biologists and Ecologists: Professionals responsible for classifying and interpreting possible impact on 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.
Technical Specifications:
Outlines sensor types, configurations, and operational requirements for data capture.
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 data collected for environmental sampling and point measurements. 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/equipment 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.
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:
-
Parent Event ID: Links the survey to a larger campaign.
-
Location ID: Identifies the survey station or area.
-
Event ID: A unique identifier for each survey.
-
Survey/Event Date: Specifies the date of the survey activity.
-
Project/Asset Name: Links the survey to a specific project or operational asset.
Format Guidelines:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Parent Event ID | Text | Unique identifier for campaign, e.g name of project or asset | Hammerfest |
| Location ID | Text | Identifier for survey location | LOC_001 |
| Event ID | Text | Unique ID for survey event | Hammerfest_LOC_001 |
| 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 | 200.45 |
| Date/Time* | Text | ISO 8601 format | 2021-06-29 T23:59:25:000+01:00 |
*Date/Time to be measured per sampling station.
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/equipment Metadata¶
Sensor metadata describes the equipment, including visual observations, 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/equipment: E.g., probe, GC/MS, visual observation, Van Veen grab, push core.
-
Sensor Carrier: Platform carrying the sensor (e.g., ROV, Vessel).
Format Guidelines:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Sensor Type | Text | Type of sensor used | Visual observation |
| Sensor Carrier | Text | Platform carrying the sensor | ROV |
Validation:
-
Validate sensor data against operational requirements (e.g., altitude and heading accuracy).
-
Ensure metadata overlays (e.g., timestamp, location).
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 provided or described in contract.
-
Standardised file naming conventions must be applied to ensure seamless integration.
3. Technical Specifications¶
3.1 Overview¶
This section outlines the technical specifications required to conduct environmental sampling and point measurements effectively. It includes the types and configurations of sensors used for data collection and the standards for data capture. Adherence to these specifications ensures high-quality data acquisition, operational consistency, and compliance with environmental standards.
The section is divided into the following subsections:
I. Sensor Types and Configurations:
Describes the recommended sensors and, if relevant, their integration with carriers.
II. Data Capture Standards:
Defines operational parameters such as calibration of sensor and/or sample size.
3.2 Sensor Types and Configurations¶
Purpose:
To provide guidelines on selecting and deploying sensors that meet technical and operational requirements for environmental sampling and point measurements.
Recommended Sensor Types:
-
Positioning Sensors, if relevant:
-
GNSS: Ensures accurate surface positioning of the vessel or ROV deployment point
-
USBL/SSBL: Provides precise subsea positioning.
-
INS (Inertial Navigation System): Enhances accuracy by correcting for drift in GNSS data.
-
Vessels operating in vicinity of infrastructure: Dynamic positioning (DP) class two is required
-
-
Sensors in accordance with authority required and/or survey specific guidelines.
Sensor Carriers, if relevant:
-
Vessels:
-
Equipped with GNSS for surface positioning.
-
Serve as the deployment platform for e.g. grab, ROV, etc.
-
-
ROVs:
- Recommended type: Working-Class ROV (WROV) for robust performance in harsh subsea environments.
Configuration Standards:
| Sensor | Carrier | Technical Requirement | Example |
|---|---|---|---|
| GNSS | Vessel | Accurate surface positioning (±1m). | Enabled for real-time tracking. |
| USBL/SSBL | ROV/grab | Subsea positioning accuracy (±0.5m). | Linked to GNSS for calibration. |
3.3 Data Capture Standards¶
Data capture shall be performed in accordance with authority required and/or survey specific guidelines.
4. Data Formats and Delivery¶
4.1 Overview¶
This section outlines the standardized data format for environmental sampling and point measurements, along with guidelines for organising and delivering the data. The format is based on GBIF reporting format.
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
4.2 File Formats¶
The individual datatypes are all based on GBIF reporting format and are to be delivered for the following categories:
-
Chemistry
-
Geology
-
Biology
4.3 File Naming Conventions¶
The individual datatypes are to be delivered in accordance with the following file naming convention: < Asset >< Survey Type >< Vendor >< Contract No>< Date >
Example: HLNG_Utslipp_Luft_NILU_4502836398_2017-05-31
4.4 Delivery protocols¶
The individual datatypes are to be delivered in accordance with the following delivery protocols:
1. Data Package:
- Include data on specified excel format, and a survey report in PDF format
2. Geospatial Data:
- Deliver point data, as part of specified excel format, for chemical measurements, geology and/or species classifications.
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
5 Integration and Reporting¶
5.1 Overview¶
Integration and reporting ensure that environmental sampling and point measurement data is properly aligned with regulatory requirements, environmental databases, and project deliverables. This section outlines the protocols for preparing, integrating, and submitting survey data and reports.
5.2 Integration Standards¶
If relevant, also country specific requirements shall be applied in addition to the specified excel format.
Validation:
- Ensure data consistency and alignment with specified reporting format before submission.
5.3 Reporting Requirements¶
Survey Report:
- Include objectives, methods, findings, and geospatial visualizations.
- Deliver in PDF format.
Deliverables:
- Measurements and associated metadata. Ensure chemical, geological and biological measurements are included in the dataset when applicable.
File Links:
- Ensure all files are referenced in the report.
5.4 Delivery Protocols¶
Submit data using portal/solution specified in contract.
Adhere to naming conventions and directory structures specified in Section 4.3.
Validate files for completeness and compliance before delivery in accordance with chapter 4.
If no country specific requirements are given, the following datatypes (DT1-DT4) are to be reported.
These tables are found here in the following Excel fill that is to be used for reporting:
GBIF Template
Environmental_samplingand_point_measurements report
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 |
| type | The nature or genre of the resource. If relevant, use the matrix or medium the sample originates from. E.g., "Muscle", "Rain". | Muscle |
| scientificName | The full scientific name. This should be the name in the lowest level taxonomic rank that can be determined. Use when measuring chemistry/properties in biological tissue. I.e., report the scientific name of the species the tissue is from. | Salmo trutta |
| 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 (chem)¶
| 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 |
| chemicalCategory | The general chemical category (optional). | Heavy metals |
| chemicalName | Chemical name according to the IUPAC standard. | Mercury |
| quantityOperator(<,> or =) | Operator related to chemicalQuantity. | = |
| chemicalQuantity | A number or enumeration value for the chemical quantity. | 0.31 |
| chemicalQuantityType | The type of quantification system used for the chemical quantity. | mg/kg dry weight |
| classificationStatus | A statement about the presence or absence of a chemical at a Location. E.g., “Present”, “Absent”. For chemistry, use “Tilstandsklasse”. | 3 |
| 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 |
| occurrenceRemarks | Comments or notes about the occurrence. | Caught in gill net |
DT3: Associated occurrences (geo)¶
| 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 endof the event was recorded. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). | 2024-09-27 |
| geologicalCategory | The general geological category (optional). | Sediment |
| geologicalName | Geological name. | Barite |
| geologicalQuantity | A number or enumeration value for the geological quantity. | 2 |
| geologicalQuantityType | The type of quantification system used for the geological quantity. | mg/kg |
| occurrenceStatus | A statement about the presence or absence of a geological feature at a Location. E.g., “Present” or “Absent”. | Absent |
| occurrenceRemarks | Comments or notes about the occurrence. | Measurement below detection limit. |
DT4: Associated occurrences (bio)¶
| 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 endof the event was recorded. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E). | 2024-09-27 |
| kingdom | The full scientific name of the kingdom in which the taxon is classified. | Animalia |
| scientificName | The full scientific name. This should be the name in the lowest level taxonomic rank that can be determined. | Paragorgia arborea |
| taxonRank | The taxonomic rank of the most specific name in the scientificName. | Species |
| organismQuantity | A number or enumeration value for the quantity of organisms. | >15 |
| organismQuantityType | The type of quantification system used for the quantity of organisms. | Specimens per 25 square meters |
| occurrenceStatus | A statement about the presence or absence of a Taxon at a Location. E.g., “Present” or “Absent”. | Present |
| occurrenceRemarks | Comments or notes about the occurrence. | Excellent coral garden |
6 Quality Assurance¶
6.1 Overview¶
Quality assurance ensures environmental sampling and point measurement data are accurate, reliable, and meet regulatory standards.
6.2 QA During Data Collection¶
Sensor Checks:
- Calibrate sensors before and after surveys.
Standards:
- If, relevant, keep sensors in required position and ensure metadata (date, time, coordinates) are recorded.
Real-Time Monitoring:
- Check data quality during collection to fix any issues immediately.
6.3 QA During Data Processing¶
File Validation:
- Ensure all files are complete, accurate, and named correctly.
Cross-Checks:
- Match metadata with data content to confirm consistency.
6.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 Environmental sampling and point measurements data meeting other requirements than specified in this document, please ensure that all deliverables meet the given regulatory standard(s)
Completeness:
- Include all required files and reference them properly in the survey report.
7 Glossary¶
The following terms and acronyms are used in this document and are defined here for clarity.
| Acronym | Explanation |
|---|---|
| DT | Data Type |
| EPSG | European Petroleum Survey Group |
| GBIF | Global Biodiversity Information Facility |
| GC/MS | Gas Chromatography Mass Spectrometry |
| GNSS | Global Navigation Satellite System |
| ID | Identification |
| INS | Inertial Navigation System |
| IUPAC | International Union of Pure and Applied Chemistry |
| NEA | Norwegian Environment Agency |
| Portable Document Format | |
| QA | Quality Assurance |
| ROV | Remotely Operated Vehicle |
| SRS | Spatial Reference System |
| SSBL | Super Short Baseline |
| USBL | Ultra-Short Baseline |
| WGS84(EPSG4326) | World Geodetic System 1984 |
| WROV | Work-Class Remotely Operated Vehicle |