Metadata and Reporting Requirements for Data Deliveries of Data Used in the Environmental Impact Assessment¶
1. Introduction¶
Purpose¶
This document outlines metadata requirements for data deliveries of data used in the Environmental Impact Assessment (EIA) and for reporting. The goal is to ensure alignment with Equinor requirements facilitating robust environmental reporting.
Scope¶
This document covers the requirements related to data deliveries utilizing existing data as part of the EIA and reporting of the EIA to Equinor, including:
- Metadata related to data used in the EIA
- File formats
- Reporting requirements
The scope of the delivery shall be in accordance with project-specific needs outlined in contract(s).
Surveys collecting new data as part of the EIA process shall follow the metadata and reporting requirements available for the specific data type(s) in question: Data Formats - SSU Documentation - for external Vendors
Target Audience¶
The intended audience for this document is contractors supporting the Environmental Impact Assessment process.
Document Structure¶
Metadata Requirements¶
Covers metadata related to the source for the data used and geospatial data.
Data Formats and Delivery¶
Specifies file formats, naming conventions, and standards for delivering.
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 Impact Assessment. It serves as the backbone for data integration, regulatory compliance, and effective environmental analysis/assessments.
This section outlines the core metadata categories necessary to support these objectives and explains their importance.
2.2 Metadata for Data Used in EIA Report¶
Captures details about the data sources, dates for downloading, and type of data. This metadata ensures traceability and documentation of the data used in the analyses.
2.3 Geospatial Metadata¶
Provides information regarding coordinate systems and, if relevant, transformation of data used in the EIA, enabling accurate mapping and spatial analysis.
Purpose:
- To ensure spatial accuracy and facilitate geospatial analyses.
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.
3. Data Formats and Delivery¶
3.1 Overview¶
This section outlines the standardized data format for the Environmental Impact Assessment deliveries.
File formats¶
- Describes the recommended file formats and their associated metadata.
File naming conventions¶
- Defines how the data is named.
Delivery protocols¶
- Defines what, how, and where the data are to be delivered.
3.2 File Formats¶
Geospatial data gathered and used as part of the EIA report shall be delivered as an ESRI File Geodatabase (FGDB).
The FGDB shall have a feature class for each collection of geographic features that share the same geometry type (point, line, and polygon).
The metadata shall include Coordinate Reference System (CRS), source, and date of download.
Example Metadata Schema¶
| FIELD NAME | DESCRIPTION | VALUE DOMAIN |
|---|---|---|
| SURVEY_ID | Project name | Free text |
| LOCATION_ID | Unique ID number for location | Number |
| NAME | The international name of the identified feature | Free text |
| NAME_ORIGINAL | Native name of the identified feature | Free text |
| COUNTRY | 2-digit ISO 3166-1 alpha-2 code | e.g. NO, LY, US |
| AREA | Greater region or area | Free text |
| FIELD | Specific geographical name of mapped area | Free text |
| CLASSIFICATION | Feature classification (areas of ecological interest, cultural heritage, hydrology, land use, geohazards, infrastructure, social, other) | Free text |
| RESOLUTION | Declared intended scale/resolution | Free text |
| SOURCE | Source of the data | Website |
| DOWNLOAD DATE | Date the data was downloaded | Date |
| COORDINATE REFERENCE SYSTEM (CRS) | CRS used in the EIA | Free text |
| TRANSFORMATION | EPSG code of the transformation if applicable | Free text |
For a more detailed description of the classifications, see Appendix A.
3.3 File Naming Conventions¶
The feature classes within the FGDB shall be delivered with the following naming convention:
Example:
The date used shall refer to the date when the data was downloaded.
3.4 Delivery Protocols¶
Deliveries shall be in accordance with the following delivery protocols:
Data Package¶
- Includes the FGDB and the report in PDF format.
Geospatial Data¶
- Deliver in accordance with specifications in Chapter 2.
Delivery Location¶
Please refer to the data delivery guidelines: Data Formats - SSU Documentation - for external Vendors
4. Integration and Reporting¶
4.1 Overview¶
This section outlines the requirements for preparing and submission of data files and reports.
4.2 Reporting Requirements¶
Description of Report¶
- Include objectives ,Deliver in PDF format.
Deliverables¶
- Data used in the EIA and associated metadata.
File Links¶
- Ensure all files are referenced in the EIA report.
4.3 Delivery Protocols¶
Submit data using the portal/solution specified in the contract.
Adhere to naming conventions and directory structures specified in Section 3.3.
If no country-specific requirements are given, the following are to be delivered:
- PDF, including the report properties specified at: Metadata and reporting requirements for environmental and biodiversity related reports - SSU Documentation - for external Vendors
5. Quality Assurance¶
File Validation¶
- Ensure all files are complete, accurate, and named correctly.
Cross-Checks¶
- Match metadata with data content to confirm consistency.
6. Glossary¶
| Acronym | Explanation |
|---|---|
| CRS | Coordinate Reference System |
| EIA | Environmental Impact Assessment |
| EPSG | European Petroleum Survey Group |
| FGDB | File Geodatabase |
| ID | Identification |
| Portable Document Format |
Appendix A – Description of Data Classification¶
Categories of data provided below serve as examples of geospatial data collected for an Environmental Impact Assessment.
Relevant data shall be delivered as points, polygons, or polylines with required attributes and metadata.
Areas of Ecological Interest¶
This should include data related to areas protected for endangered flora or fauna, or important areas for certain species:
- International, national, or local designated protected areas
- Important habitats for endangered species (flora and fauna)
- Important breeding grounds
- Ancient woodland
- Conservation areas (onshore/offshore)
Cultural Heritage¶
This should include data for internationally designated areas as well as areas designated as conservation areas (with respect to cultural heritage), listed or protected buildings/structures.
Hydrology¶
This should include data related to:
- Water bodies
- Rivers
- Drainage basins
- Watersheds
Land Use¶
This should include data related to how land is used, such as:
- Agricultural land
- Natural lands
- Built-up areas
Geohazards¶
This should include data for geological hazards such as:
- Landslides
- Ground subsidence
- Erosion
- Flooding
Infrastructure¶
This should include data related to access and transmission infrastructure, such as:
- Roads
- Ports
- Airports
- Power lines
- Pipelines
- Wind farms
- Man-made dams
Social¶
This should include data related to social impacts, such as:
- Residential areas
- Public services
- Schools
- Hospitals
- Employment areas