© 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: 2022, XOCEAN, Dudgeon, Asset Integrity Survey
Abstract:
During June 2022 XOCEAN were asked by Reach Subsea AS to perform a full site survey on behalf of Equinor within the Dudgeon OWF. Data was acquired over the full area of the Dudgeon OWF and one export cable route. A single survey campaign was conducted from July 31st to October 16th 2022. The survey objective was to use a multibeam echosounder to collect suitable data coverage and density to identify any items larger than 0.5 m. - 1 m Digital Terrain Model (DTM). - Achieve a sounding density of 5 hits per 1 m cell. - Feature picking of objects greater than 0.5 metres.
Data holder:
The Crown Estate
| Other details | ||
| Internal code | Internally assigned metadata identifier | 19259 |
| 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. | 2022, XOCEAN, Dudgeon, Asset Integrity Survey |
| Alternative title | The purpose of alternative title is to record any additional names by which the dataset may be known. | Asset Integrity Survey |
| 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. | 86bacba5-44b8-49e3-86a1-f3b62f351de4 |
| Resource Identifier | This is the code assigned by the data owner. | TCE-3687 |
| 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. | series |
| Start date | This describes the date the resource starts. This may only be the year if month and day are not known | 2022-07-31 |
| End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2022-10-16 |
| Spatial resolution | This describes the spatial resolution of the dataset or the spatial limitations of the service. | 1 |
| Spatial resolution unit | This describes the unit of spatial resolution which for distance must be metres. | urn:ogc:def:uom:EPSG::9001 |
| 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. | During June 2022 XOCEAN were asked by Reach Subsea AS to perform a full site survey on behalf of Equinor within the Dudgeon OWF. Data was acquired over the full area of the Dudgeon OWF and one export cable route. A single survey campaign was conducted from July 31st to October 16th 2022. The survey objective was to use a multibeam echosounder to collect suitable data coverage and density to identify any items larger than 0.5 m. - 1 m Digital Terrain Model (DTM). - Achieve a sounding density of 5 hits per 1 m cell. - Feature picking of objects greater than 0.5 metres. |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | 9.1. Online and Offline Quality Assurance The provided windfarm area was used as a base for the survey areas. The sounding density was monitored online in the NavAQ navigational/logging software to accurately meet the survey requirements. After completion of each of the survey areas the data was checked to ensure its quality. If grid nodes with low density were identified, supplementary infill survey lines were run. Hull-mounted Norbit Winghead MBES data was collected in NavAQ and stored in Raw *.bwx files. The Primary Reference Position (online) was provided by an Applanix POS MV system, augmented with Marinestar corrections in real time to establish a horizontal position accurate to less than 0.1 m, and a vertical position accurate to less than 0.15 m. The POS MV combines Global Navigation Satellite System (GNSS) and Inertial Measurement Unit (IMU) data into a tightly coupled integrated navigation solution. Preliminary coverage and data quality checks were made in Beamworx Autoclean software. Data download took place when the USV came back to port, via a Universal Serial Bus (USB) connection. The data was copied onto an external hard drive, and from there it was transferred to the XOCEAN storage servers for processing. The data is not deleted from the USV until the transfer to the servers has been verified. 9.2. MBES Data Processing Method and Quality Assurance A Post Processed Kinematic (PPK) solution was derived for the shipâ??s navigation using Applanix POSPac MMS (version 8.7) and the Trimble VRS-Now corrections. This uses GPS data logged online and high accuracy reference station based GNSS combined with wide-area coverage global satellite corrections. This network of stations can generate precise orbit, clock, and observation biases, which are transmitted to POSPac and used for tightly coupled inertial processing. This navigation solution was later applied to the sounding data in Autoclean. The data was reduced to MSL using the UKHO VORF MSL geoid model. The data was corrected with the observed sound velocity profiles to adjust for refraction effects. The sound velocity profiles and correlation with the MBES sound velocity sensor can be observed in Figure 11. The data was cleaned utilising the 95% confidence standard deviation layer and then quality checked for any spikes using the shallow, deep, and 3D view |
| Related keywords | ||
| Keyword | General subject area(s) associated with the resource, uses multiple controlled vocabularies | Sound velocity and travel time in the water column |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Bathymetry and Elevation | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Post-Construction monitoring | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Renewable Energy Lease area | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Hydrography | |
| Geographical coverage | ||
| North | The northern-most limit of the data resource in decimal degrees | 53.316 |
| East | The eastern-most limit of the data resource in decimal degrees | 1.45 |
| South | The southern-most limit of the data resource in decimal degrees | 52.95 |
| West | The western-most limit of the data resource in decimal degrees | 1.13 |
| 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 | The Crown Estate | |
| Position name | Marine Data Advisor | |
| Phone | +44 020 7851 5000 | |
| enquiries@thecrownestate.co.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 | The Crown Estate | |
| Phone | +44 020 7851 5000 | |
| enquiries@thecrownestate.co.uk | ||
| Role | The originator is the person or organisation who created, collected or produced the resource. | originator |
| Organisation name | XOCEAN | |
| Position name | Data Processor | |
| data.processor@xocean.com | ||
| Role | The distributor is the person or organisation that distributes the resource. | distributor |
| Organisation name | The Crown Estate | |
| Phone | +44 020 7851 5000 | |
| enquiries@thecrownestate.co.uk | ||
| Role | The owner is the person or organisation that owns the resource. | owner |
| Organisation name | Reach Subsea | |
| post@reachsubsea.com | ||
| Resource locators | ||
| Locator URL | Web address (URL) that links to the resource | https://www.marinedataexchange.co.uk/details/TCE-3687/summary |
| Web address (URL) that links to the resource | https://www.marinedataexchange.co.uk | |
| Dataset constraints | ||
| 20.1 Limitations on Public Access - Access constraints | This states `otherRestrictions` from ISO vocabulary RestrictionCode and is an INSPIRE/GEMINI requirement. | otherRestrictions |
| 20.2 Limitations on Public Access - Other constraints | Once published, there will be no limitations on public access. Data must be used in accordance with the Marine Data Exchanges Terms of Use which can be found on the website. | |
| 21.1 Conditions for Access and Use - Use constraints | This states `otherRestrictions` from ISO vocabulary RestrictionCode and is an INSPIRE/GEMINI requirement. | otherRestrictions |
| 21.2 Conditions for Access and Use - Other constraints | 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. | Once published, there will be no constraints on access and use. Data must be used in accordance with the Marine Data Exchanges Terms of Use which can be found on the website. |
| 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. | 2025-05-30 |
| Date of last revision | The most recent date that the resource was revised. | 2023-10-26 |
| Date of creation | The date that the resource was created. | 2022-10-16 |
| 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. | 2026-02-05 |
| Metadata standard name | The name of the metadata standard used to create this metadata | MEDIN |
| Metadata standard version | The version of the MEDIN Discovery Metadata Standard used to create the metadata record | 3.1.2 |