© OpenStreetMap contributors
- Add External Layer
- Upload Shapefile
- Layer Tutorial
- Close
Use the checkbox () to show or hide a layer.
Use the radio buttons () to select a layer to use with the identify function.
- Layers
- Opacity
Available layers
(ctrl+c)
Search for marine data across UK organisations
- API
- How-To
- About
- Contact MEDIN
- Share
Metadata: 11209 HOW03 GP1B Lot 4 Geophysical UHR Survey 2018 - SSS
Abstract:
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
Data holder:
Gardline Limited
Click on the red button for resource contact details:
- Click on the red button for resource contact details
Use constraints:
Use of this data requires approval from Orsted
| Other details | ||
| Internal code | Internally assigned metadata identifier | 2270 |
| 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 - SSS |
| 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. | 981acf7d1e90a8d7eb0235a252c37251 |
| 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. | Raw sidescan sonar XTF and JSF, low frequency (300kHz), medium frequency (600kHz) and high frequency (900kHz), Vessel: M.V. Ocean Endeavour. Equipment Type: Edgetech Side Scan Sonar FS4200 600/300kHz and 900/300kHz. Ping Rate: 10 per second for 600/300kHz and 30 per second for 900/300kHz. Range Setting: 80m for 600/300kHz and 25m for 900/300kHz. Data Resolution Along Track: 0.4m for 600/300kHz and 0.1m for 900/300kHz. Data Resolution Across Track: 0.03m for 300kHz, 0.015m for 600kHz and 0.01m for 900kHz. All USBL navigation has been processed using Gardline in-house Voyager5 software. Data processing has not been carried out on this dataset. Heading corrections were carried out using Gardline in-house Geofusion software using a rolling heading based on course over ground with further manual adjustments as required. Data was recorded in both jsf and xtf format using Edgetech Discover software Version 33.0.1.109. Deliverable created using: Gardline in-house Geofusion software. Total Positional Uncertainty derived from the USBL data - 0.4% at 1DRMS. Sidescan Sonar Navigation File, Vessel: M.V. Ocean Endeavour Equipment Type: Edgetech 4200 Sonar Fish and Sonardyne Ranger USBL System. Navigation Data Processing were carried out using Voyager5 and deliverables were created using Gardline in House Voyager5 Software. USBL data were processed and raw data were opened in Voyager5 and manually checked and corrected for any spikes or erroneous points. Once data cleaning has been carried out a light smooth filter of 11 points was added to the data which was then exported in a cnv format. Total Positional Uncertainty derived from the USBL data - 0.4% at 1DRMS. Sidescan Sonar Mosaic, high frequency (600kHz) and low frequency (300kHz), Vessel: M.V. Ocean Endeavour Equipment Type: Edgetech Side Scan Sonar FS4200 600/300kHz. All USBL navigation has been processed using Gardline in-house Voyager5 software. Data has been cleaned and a smooth filter applied to the track. Data processing has been carried out using Gardline in-house Geofusion software. Raw XTF files are read in, corrected navigation is applied, the seabed is tracked, TVG's are applied and data is mosaiced using the cover-up method. Targets are then compared with final bathymetry. Total Positional uncertainty calculated from the USBL data is 0.4% 1DRMS although additional uncertainties are introduced due to the variable nature of the actual sonar fish heading. Data Resolution: 10cm and 1.0m. Along Track Resolution - 0.1m, Across Track Resolution - 0.01m. Background Value: 255,255,255. 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. Contact images JPG and GeoTIF. Vessel: M.V. Ocean Endeavour. Equipment Type: Fugro Starpack Navigation Package, Edgetech FS4200 300/600kHz, 300/900kHz Side scan sonar and Sonardyne Ranger USBL System. Side scan sonar data were interpreted using Gardline's Geofusion software for potential seabed contacts and where present PDFs produced. Total Positional Uncertainty derived from the Ranger 2 USBL System 0.4% 1DRMS. 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. 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. 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 assess 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. An image of the sonar data is then exported as a JPG image at a resolution of 0.1m, this is centred on the position of the target on the side scan sonar data rather than the MBES position. |
| 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 | |
| dassh.enquiries@mba.ac.uk | ||
| 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 | |
| dassh.enquiries@mba.ac.uk | ||
| 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 | |
| dassh.enquiries@mba.ac.uk | ||
| 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 | |
| dassh.enquiries@mba.ac.uk | ||
| Dataset constraints | ||
| 20 Limitations on Public Access - Access constraints | otherRestrictions | |
| 20 Limitations on Public Access - Other constraints | This states any limitations on access to the data and uses free text. | Use of this data requires approval from Orsted |
| 21 Conditions for Access and Use - Use limitation | This states any constraints on use of the data. Multiple conditions can be recorded for different parts of the data resource. If no conditions apply, then `No condtions apply` is recorded. This uses free text. | 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 |
| Harvest date | The date which this record has been (re)harvested from the provider. | 2026-04-12 |
| 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 |