© 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: 2018_023_HOW03_Lot8_Sample_B01_SBP_data
Abstract:
Bibby HydroMap were commissioned in May 2018 by Orsted to carry out Geophysical and Benthic surveys at Horsea 03 Lots 5 and 8. The survey across the Lot 8 export route was completed under Bibby HydroMap's terms and conditions using MV Bibby Tethra, between 16th August and 3rd September 2018 with a 40m line spacing. The main objectives of the surveys were as follows: â?¢ Cable route engineering â?¢ Geo-hazard assessment â?¢ Consenting requirements o Identifying archaeological restrictions o Identifying protected ecological habitats â?¢ Planning of Geotechnical investigations â?¢ UXO clearance for Geotechnical investigations This dataset comprises of the subbottom data across the survey area.
Data holder:
Bibby HydroMap Ltd
Click on the red button for resource contact details:
- Click on the red button for resource contact details
Use constraints:
Not for public distribution
| Other details | ||
| Internal code | Internally assigned metadata identifier | 942 |
| 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. | 2018_023_HOW03_Lot8_Sample_B01_SBP_data |
| 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. | 3be637a9c6f04d87c4a4003371fe47f1 |
| Resource Identifier | This is the code assigned by the data owner. | 2018_023 |
| 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-08-16 |
| End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2018-09-03 |
| 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'. | notPlanned |
| Abstract | The abstract provides a clear and brief statement of the content of the resource. | Bibby HydroMap were commissioned in May 2018 by Orsted to carry out Geophysical and Benthic surveys at Horsea 03 Lots 5 and 8. The survey across the Lot 8 export route was completed under Bibby HydroMap's terms and conditions using MV Bibby Tethra, between 16th August and 3rd September 2018 with a 40m line spacing. The main objectives of the surveys were as follows: â?¢ Cable route engineering â?¢ Geo-hazard assessment â?¢ Consenting requirements o Identifying archaeological restrictions o Identifying protected ecological habitats â?¢ Planning of Geotechnical investigations â?¢ UXO clearance for Geotechnical investigations This dataset comprises of the subbottom data across the survey area. |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | Vertical Datum: BLAST LAT Horizontal Datum: ETRS89 Projected co-ordinate system: ETRS89 UTM Zone 31 North Transformation: from WGS84 to ETRS89 using 7-parameter Helmert at epoch 2018.7 Vessel: MV Bibby Tethra Equipment: Innomar SES-2000 Medium, iXBlue Hydrins INS, C-Nav integrated with Hydrins INS data Software: RadExPro, IHS Kingdom software, RUSH, In-house scripts in Python, QPS QINSy, Positional uncertainty: 0.15m (horizontal); 0.2m (vertical) Horizontal resolution: 0.20m Vertical resolution: 0.09m Ping rate: 11pps Central frequency: 10KHz Pulse cycles: 1 pulse Recording range: Variable recorded trace length 55.332, 62.004 and 68.664 ms; set to 72.000ms for vertical correction to Datum, to prevent cutting off unwanted record during vertical correction. Raw SEGY: SBP data acquired using Innomar acquisition system as SES and RAW format. Hydrins WGS84 positioning and time stamp with no latency and motion correction embedded online in Trace Header data. Raw SEG-Y files exported using SES-Convert. Positioning in ETRS89 UTM31N exported from QINSy offline (to remove latency), corrected for any navigation drop outs using in-house scripts in Python to be subsequently embedded in the SEG-Y Trace Headers by time stamp. Processed SEGY-Y: Processed SEG-Y files with calculated navigation, motion correction and tidal reduction from QINSY output for every ping. Vertical correction to Datum carried in RadExPro software from; no processing (filters, gains, etc) applied. SEG-Y data in two way travel time. Final data exported fromRadExPro and QC'ed in IHS Kingdom software. Small percentage of files with a static shift of 0.2ms applied in RADEXPRO Navigation QINSy calculated position, computed for Innomar node using C-Nav with the C-NavC2 correction service and iXBlue Hydrins INS data; Logfiles exported offline (to remove latency) from QPS QINSy navigation software at 1Hz. Any nav drop outs were removed and positions interpolated using in-house scripts in Python. Tide Correction File Logfiles exported online from Qinsy navigation software at 1Hz including Innomar sensor GNSS height and sound velocity from mini-SVS adjacent to MBES transducer. Polynomial smoothing applied to reduced GNSS heights using MatLAB scripted software RUSH. Smoothed reduced height converted to time using logged Mini-SVS sound velocities. GNSS height files per day. Extra fields included - smoothed sensor height, speed of sound at the MBES transducer and smoothed sensor height in milliseconds (microsecond accuracy); Tide File Format: Date, Hours, Min, Seconds, Raw GNSS Height, SV, Smoothed GNSS Height, Time delay (ms). Motion Correction Logfiles exported online from QPS QINSy navigation software at 1Hz (before being set up to 25Hz) including heave, pitch and roll at Innomar node. Trackplots QINSy 1Hz navigation logfiles interpolated for every sub-bottom data trace and applied to SEG-Y data using in-house scripts in Python (any nav drop outs were removed and positions interpolated). Positioning exported from SEG-Y Trace Header files using RADEXPRO software at sensor ping rate. Trackplot line and point generation in ArcGIS. using in-house scripts in Python. Point shp decimation - points every 200 pings, including ping at start of line Line shp decimation - approx 10 points a second (all pings included). |
| 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 | Geology | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Seismic reflection | |
| Geographical coverage | ||
| North | The northern-most limit of the data resource in decimal degrees | 53.1619 |
| East | The eastern-most limit of the data resource in decimal degrees | 1.1402 |
| South | The southern-most limit of the data resource in decimal degrees | 52.9341 |
| West | The western-most limit of the data resource in decimal degrees | 0.7557 |
| 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 | Bibby HydroMap Ltd | |
| Individual name | Ben Smith | |
| Position name | CAD/GIS Technician | |
| Ben.Smith@bibbyhydromap.com | ||
| Role | The distributor is the person or organisation that distributes the resource. | distributor |
| Organisation name | Bibby HydroMap Ltd | |
| Individual name | Theo Gaussen | |
| Position name | Senior Geophysicist | |
| dassh.enquiries@mba.ac.uk | ||
| Role | The originator is the person or organisation who created, collected or produced the resource. | originator |
| Organisation name | Bibby HydroMap Ltd | |
| Individual name | Theo Gaussen | |
| Position name | Senior Geophysicist | |
| 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 | Bibby HydroMap Ltd | |
| Individual name | Theo Gaussen | |
| Position name | Senior Geophysicist | |
| 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. | Not for public distribution |
| 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. | Not suitable for use in navigation |
| 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-11-16 |
| Harvest date | The date which this record has been (re)harvested from the provider. | 2026-04-19 |
| Metadata date | The date when the content of this metadata record was last updated. | 2018-11-27 |
| 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 |