© 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
Search for marine data across UK organisations
- API
- How-To
- About
- Contact MEDIN
- Share
Metadata: 2012, Eurotech, Zone 9 - Celtic Array, QC and Interpretation of Irish Sea Zone 2D Seismic Dataset
Abstract:
The Round 3 Development project acquired a large 2D Seismic dataset in the Irish Sea Zone (ISZ) in 2010. The data was acquired by MMT (Sweden) using Triton Elics acquisition software and Interpreted to 50m depth (or to Seabed where shallower than 50m) as per the framework contract. The data was delivered to CERI in April 2011 as Raw SEGY files and loaded to Kingdom projects (Geophysical Software), with interpreted horizons and grids. Since receiving the data, a number of Consultants (see Appendix I) raised significant concerns with the data quality, the way the data had been loaded to Kingdom, the way the data have been interpreted and the method used by MMT for tidally correcting the data. Therefore, the decision was made for CERI to reload, QC and re-interpret (where necessary) the data in-house to ensure data integrity and consistency in approach with regard to loading and interpretation.
Data holder:
The Crown Estate
| Other details | ||
| Internal code | Internally assigned metadata identifier | 27585 |
| 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. | 2012, Eurotech, Zone 9 - Celtic Array, QC and Interpretation of Irish Sea Zone 2D Seismic Dataset |
| Alternative title | The purpose of alternative title is to record any additional names by which the dataset may be known. | QC and Interpretation of Irish Sea Zone 2D Seismic Dataset |
| 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. | c956741c-bf7e-4b6d-a968-2cee37c8f459 |
| Resource Identifier | This is the code assigned by the data owner. | TCE-2653 |
| 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 | 2012-01-01 |
| End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2012-01-01 |
| Spatial resolution | This describes the spatial resolution of the dataset or the spatial limitations of the service. | 3700 |
| 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'. | unknown |
| Abstract | The abstract provides a clear and brief statement of the content of the resource. | The Round 3 Development project acquired a large 2D Seismic dataset in the Irish Sea Zone (ISZ) in 2010. The data was acquired by MMT (Sweden) using Triton Elics acquisition software and Interpreted to 50m depth (or to Seabed where shallower than 50m) as per the framework contract. The data was delivered to CERI in April 2011 as Raw SEGY files and loaded to Kingdom projects (Geophysical Software), with interpreted horizons and grids. Since receiving the data, a number of Consultants (see Appendix I) raised significant concerns with the data quality, the way the data had been loaded to Kingdom, the way the data have been interpreted and the method used by MMT for tidally correcting the data. Therefore, the decision was made for CERI to reload, QC and re-interpret (where necessary) the data in-house to ensure data integrity and consistency in approach with regard to loading and interpretation. |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | QC and interpretation carried out by Eurotech, on behalf of CERI. Raw data QC and Interpretation work: To QC the seismic data, all lines from the ISZ and Met Mast surveys were loaded to new Kingdom projects to check the expected files had been delivered, would load properly and to check the data quality. All the SEGY data was loaded with the navigation taken from the SEGY headers; shotpoints located in byte 9 and all co-ordinates multiplied by 0.01 on import. The data was checked for the line existing, the line format, navigation in the header and a rating of the data quality (QC observatons noted in spreadsheet: R3-D-EN-088-0000-000000-018). Interpretation was carried out, including tidal correction, gridding and creation of isopach maps. Further information is available in report: R3-D-EN-078-0000-000000-019 |
| Related keywords | ||
| Keyword | General subject area(s) associated with the resource, uses multiple controlled vocabularies | Sedimentary structure |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Seismic reflection | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Seismic refraction | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Geotechnics | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Consenting | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Zone search area | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Elevation | |
| Geographical coverage | ||
| North | The northern-most limit of the data resource in decimal degrees | 53.9755 |
| East | The eastern-most limit of the data resource in decimal degrees | -3.6694 |
| South | The southern-most limit of the data resource in decimal degrees | 53.4913 |
| West | The western-most limit of the data resource in decimal degrees | -5.0537 |
| 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 | Centrica Energy Renewable Investments (CERI) | |
| Position name | GIS and Data Manager | |
| CERI@centrica.com | ||
| 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 | Eurotech Computer Services Ltd | |
| sales@eurotech-computers.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 | Centrica Energy Renewable Investments (CERI) | |
| CERI@centrica.com | ||
| Resource locators | ||
| Locator URL | Web address (URL) that links to the resource | https://www.marinedataexchange.co.uk/details/TCE-2653/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 | There will be no limitations when published on the Marine Data Exchange | |
| 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. | Data Must be used in accordance to the Marine Data Exchange's Terms of Use: https://www.marinedataexchange.co.uk/content/info/terms-of-use |
| 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. | 2021-05-17 |
| Date of creation | The date that the resource was created. | 2012-03-09 |
| Harvest date | The date which this record has been (re)harvested from the provider. | 2026-05-06 |
| Metadata date | The date when the content of this metadata record was last updated. | 2026-05-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 |