© OpenStreetMap contributors
Wind Farm Identifier: HOW03 LOT4; Survey Details: Geophysical 1b pre-geotechnical UXO survey acquiring magnetometer array, bathymetry, side scan sonar, sub bottom profiler, ultra-high resolution multichannel seismic and environmental grab sample data across wind farm and along export cable corridor. Acquired by Gardline Limited. Geophysical Acquisition Dates 2018-05-01 to 2018-09-07. Projection: Horizontal datum: ETRS89 (2018.0) Ellipsoid name: GRS 1980 Coordinate system: UTM 31N Vertical Datum LAT
Gardline Limited
Use of this data requires approval from Orsted
Other details | ||
Internal code | Internally assigned metadata identifier | 4913 |
Title | The title is used to provide a brief and precise description of the dataset such as 'Date', 'Originating organisation/programme', 'Location' and 'Type of survey'. All acronyms and abbreviations should be reproduced in full. | 11209 HOW03 GP1B Lot 4 Geophysical UHR Survey 2018 - Backscatter |
File Identifier | The File Identifier is a code, preferably a GUID, that is globally unique and remains with the same metadata record even if the record is edited or transferred between portals or tools. | bdcacd10554d0a216f0dd602d8430fb7 |
Resource Identifier | This is the code assigned by the data owner. | 11209 |
Resource type | The resource type will likely be a dataset but could also be a series (collection of datasets with a common specification) or a service. | dataset |
Start date | This describes the date the resource starts. This may only be the year if month and day are not known | 2018-05-01 |
End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2018-09-07 |
Vertical extent (min) | A positive or negative decimal number, for example, the shallowest depth recorded if subtidal, or, if intertidal, the lowest point recorded. | 26.9800 |
Vertical extent (max) | A positive or negative decimal number, for example, the deepest depth recorded if subtidal, or, if intertidal, the highest point recorded. | 72.9100 |
Vertical extent reference | This descibes the vertical coordinate reference system as referred to in the EPSG register of geodetic parameters. (epsg-registry.org) | urn:ogc:def:crs:EPSG::5861 |
Spatial resolution | This describes the spatial resolution of the dataset or the spatial limitations of the service. | inapplicable |
Frequency of updates | This describes the frequency with which the resource is modified or updated i.e. a monitoring programme that samples once per year has a frequency that is described as 'annually'. | continual |
Abstract | The abstract provides a clear and brief statement of the content of the resource. | Wind Farm Identifier: HOW03 LOT4; Survey Details: Geophysical 1b pre-geotechnical UXO survey acquiring magnetometer array, bathymetry, side scan sonar, sub bottom profiler, ultra-high resolution multichannel seismic and environmental grab sample data across wind farm and along export cable corridor. Acquired by Gardline Limited. Geophysical Acquisition Dates 2018-05-01 to 2018-09-07. Projection: Horizontal datum: ETRS89 (2018.0) Ellipsoid name: GRS 1980 Coordinate system: UTM 31N Vertical Datum LAT |
Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | Backscatter X,Y,Intensity Grid, 0.25m x 0.25m, Vessel: M.V. Ocean Endeavour. Equipment Type: EM2040D Multibeam Echo Sounder 200/400kHz. Data processing has been carried out using Caris Hips and Sips v. 10.4. Tidal elevations and positioning are derived by post-processing GNSS and motion data logged throughout the survey period to produce a highly accurate vessel position and to recover the full spectrum of motion â?? heave, squat, settlement and tide. The raw GNSS/IMU data is post-processed using Terrapos to achieve a tightly-coupled PPP/INS solution. The Smoothed Best Estimate of Trajectory (SBET) output from Terrapos contains the position and motion data, together with error estimates for the multibeam transducer location. The processed GNSS heights and positions are reported in ETRS89 (2018.0) reference frame, referred to the GRS80 reference ellipsoid, exported from Terrapos. The SBET file is applied to data in Caris on a line by line basis to derive a GNSS tide. This element of the processing essentially removes the measured heave from the bathymetry and substitutes the processed SBET GNSS altitude. The SBET file is output relative to the transducer to ensure heave is computed for this location. Due to this, in order to correctly compute GNSS tide within Caris, the Reference point to Transducer Z value must be included in the GNSS tide calculation as a height correction. Data were converted from raw format using Caris 10.4. Once converted navigation and attitude data were checked and a smooth applied to the navigation, any spikes were manually removed. Following this tides were applied to the dataset. Data were then gridded and added to a base surface. Data were then checked for spikes and any artefacts and manually edited. Backscatter processing was carried out in Caris 10.4 using the geocoder engine. Gain normalised over full survey area using automatic TVG, a small filter width adaptive AVG filter, also it used the underlying DTM for full radiometric corrections. Data were then output as an XYZ, an geotif and FLT file â?? generated from the geotif in Global Mapper v15. Seafloor Contact List Combined and Cross Correlated Between SSS, Backscatter and MBES Datasets. Vessel: M.V. Ocean Endeavour. Equipment Type: Fugro Starpack Navigation Package Kongsberg Simrad EM2040D Multi-Beam Echosounder, Edgetech FS4200 300/600kHz, 300/900kHz Side scan sonar and Geometrics G882 magnetometer. Data Processing carried out using Blue Marble Geophysicsâ?? Global Mapper, Geosoftâ??s Oasis Montaj and Gardline in-house Geofusion. Total Positional Uncertainty derived from the Fugro Starpack Navigation System - 0.1m. The minimum thresholds for target analysis were 2nT for magnetometer data and 0.1m in any dimension for side scan sonar data. A confidence scale has been applied based on the number of data sets each target has been seen on: 1 - identified on one data file from one sensor only, 2 â?? Identified on multiple data files from the same sensor, contacts too dense to reconcile individual objects, 3 â?? Identified on multiple data files from one sensor only â?? position reconciled between files, 4 - Identified on data files from multiple sensors â?? position reconciled between files, 5 â?? Position and interpretation verified with background information i.e. a target identified on MBES, SSS and MAG datasets will have a confidence interval of 3. Each dataset was reviewed individually for targets which were then all loaded into Global Mapper along with the DTM, sonar mosaics, and magnetometer grids to asses which targets related to one another. Where targets we identified on different systems they were resolved to a single target, but the information from the other datasets was retained, i.e. an object identified on both MBES data and side scan sonar data will use the MBES position, but the dimensions from the sonar data. Contacts are classified as boulder unless there is an associated magnetic anomaly, in which case the contact is classified as debris. Where there is uncertainty as to the classification of a contact, it is classified as an unknown target. Contacts associated with known infrastructure will be classified as their known name. Other classifications will include wreck and fishing equipment/pots. |
Related keywords | ||
Keyword | General subject area(s) associated with the resource, uses multiple controlled vocabularies | Marine Environmental Data and Information Network |
General subject area(s) associated with the resource, uses multiple controlled vocabularies | Elevation | |
General subject area(s) associated with the resource, uses multiple controlled vocabularies | Hydrography | |
General subject area(s) associated with the resource, uses multiple controlled vocabularies | Bathymetry and Elevation | |
Geographical coverage | ||
North | The northern-most limit of the data resource in decimal degrees | 54 |
East | The eastern-most limit of the data resource in decimal degrees | 2.79 |
South | The southern-most limit of the data resource in decimal degrees | 53.69 |
West | The western-most limit of the data resource in decimal degrees | 2.21 |
Responsible organisations | ||
Role | The point of contact is person or organisation with responsibility for the creation and maintenance of the metadata for the resource. | pointOfContact |
Organisation name | Gardline Limited | |
Individual name | David Gordon | |
Position name | Principle Client Reporting Manager | |
Role | The distributor is the person or organisation that distributes the resource. | distributor |
Organisation name | Gardline Limited | |
Individual name | David Gordon | |
Position name | Principle Client Reporting Manager | |
Role | The originator is the person or organisation who created, collected or produced the resource. | originator |
Organisation name | Gardline Limited | |
Individual name | David Gordon | |
Position name | Principle Client Reporting Manager | |
Role | The custodian is the person or organisation that accepts responsibility for the resource and ensures appropriate care and maintenance. If a dataset has been lodged with a Data Archive Centre for maintenance then this organisation is be entered here. | custodian |
Organisation name | Gardline Limited | |
Individual name | David Gordon | |
Position name | Principle Client Reporting Manager | |
Dataset constraints | ||
20 Limitations on Public Access - Access constraints | ISO restriction code chosen from ISO 19115-1 Codelist | otherRestrictions |
20 Limitations on Public Access – Other constraints | Any restriction on the use of the resource such as the need to agree to certain licence conditions. | Use of this data requires approval from Orsted |
21 Conditions for Access and Use - Use limitation | Any restrictions imposed on accessing the resource such as the need to agree to certain licence conditions. | Use of this data requires approval from Orsted |
Version info | ||
Date of publication | The publication date of the resource or if previously unpublished the date that the resource was made publicly available via the MEDIN network. | 2018-09-19 |
Metadata date | The date when the content of this metadata record was last updated. | 2018-10-10 |
Metadata standard name | The name of the metadata standard used to create this metadata | MEDIN Discovery metadata standard |
Metadata standard version | The version of the MEDIN Discovery Metadata Standard used to create the metadata record | 2.3.8 |
© OpenStreetMap contributors