© 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: Project Nemo UK-Belgium Electrical Interconnector Richborough to West Zeebrugge
Abstract:
Wessex Archaeology was commissioned by PMSS, on behalf of Elia Asset S.A. and National Grid International Ltd. to carry out an archaeological desk-based assessment for the Project Nemo UK-Belgium Electrical Interconnector cable route. The cable extended approximately 130 km between Pegwell Bay in Kent to West-Zeebrugge in Belgium, and the cable route was buffered by 500 m on either side to produce a study area. At the Kent landfall, there were two listed buildings and 67 other archaeological sites and findspots, dating from the Neolithic to modern period. In English, French and Belgian Waters, there were: 8 sites of anthropogenic origin identified or confirmed with archaeological assessment of geophysical survey data (3 wrecks recorded by UKHO, SHOM and VIOE, 1 previously unrecorded wreck site and 4 further geophysical anomalies of archaeological interest); 254 additional geophysical anomalies of possible archaeological interest; a number of channels of probable prehistoric date and potential archaeological interest; and 24 additional wrecks recorded by UKHO, SHOM and VIOE but outside of the geophysical survey coverage. At the Belgian landfall there were 37 archaeological sites and findspots dating from the Roman period to the modern period, plus numerous findspots on the beach. The baseline assessment also revealed further potential for as yet undiscovered sites and material dating from the Palaeolithic to the modern period, including terrestrial sites and findspots, submerged prehistoric material, shipwrecks, aircraft crash sites and related material.
Data holder:
Archaeology Data Service
| Other details | ||
| Internal code | Internally assigned metadata identifier | 11563 |
| 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. | Project Nemo UK-Belgium Electrical Interconnector Richborough to West Zeebrugge |
| 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. | c136e9a7-4eb9-325d-89c6-c6d6f363aa03 |
| Resource Identifier | This is the code assigned by the data owner. | wessexar1-346706 |
| 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 | 2010-10-01 |
| End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2016-07-25 |
| 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. | Wessex Archaeology was commissioned by PMSS, on behalf of Elia Asset S.A. and National Grid International Ltd. to carry out an archaeological desk-based assessment for the Project Nemo UK-Belgium Electrical Interconnector cable route. The cable extended approximately 130 km between Pegwell Bay in Kent to West-Zeebrugge in Belgium, and the cable route was buffered by 500 m on either side to produce a study area. At the Kent landfall, there were two listed buildings and 67 other archaeological sites and findspots, dating from the Neolithic to modern period. In English, French and Belgian Waters, there were: 8 sites of anthropogenic origin identified or confirmed with archaeological assessment of geophysical survey data (3 wrecks recorded by UKHO, SHOM and VIOE, 1 previously unrecorded wreck site and 4 further geophysical anomalies of archaeological interest); 254 additional geophysical anomalies of possible archaeological interest; a number of channels of probable prehistoric date and potential archaeological interest; and 24 additional wrecks recorded by UKHO, SHOM and VIOE but outside of the geophysical survey coverage. At the Belgian landfall there were 37 archaeological sites and findspots dating from the Roman period to the modern period, plus numerous findspots on the beach. The baseline assessment also revealed further potential for as yet undiscovered sites and material dating from the Palaeolithic to the modern period, including terrestrial sites and findspots, submerged prehistoric material, shipwrecks, aircraft crash sites and related material. |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | This metadata was prepared by the creator entered into the OASIS system hosted by the Archaeology Data Service. |
| Additional information | This describes relevant references to the data e.g. reports, articles, websites plus other useful information not captured elsewhere. | Wessex Archaeology (2016) Project Nemo UK-Belgium Electrical Interconnector Richborough to West Zeebrugge: Archaeological Environmental Impact Assessment: Volume I: Report, 73390.03. Wessex Archaeology: Salisbury ; Wessex Archaeology (2016) Project Nemo UK-Belgium Electrical Interconnector Richborough to West Zeebrugge: Archaeological Environmental Impact Assessment: Volume II: Appendices, 73390.03. Wessex Archaeology: Salisbury |
| 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 | Protected sites | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Marine archaeology | |
| Geographical coverage | ||
| North | The northern-most limit of the data resource in decimal degrees | 51.387209116965 |
| East | The eastern-most limit of the data resource in decimal degrees | 3.2244873046875 |
| South | The southern-most limit of the data resource in decimal degrees | 51.210324789481 |
| West | The western-most limit of the data resource in decimal degrees | 1.3591 |
| 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 | Archaeology Data Service | |
| help@archaeologydataservice.ac.uk | ||
| Role | The owner is the person or organisation that owns the resource. | owner |
| Organisation name | Wessex Archaeology | |
| info@wessexarch.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 | Archaeology Data Service | |
| help@archaeologydataservice.ac.uk | ||
| Role | The originator is the person or organisation who created, collected or produced the resource. | originator |
| Organisation name | Wessex Archaeology | |
| info@wessexarch.co.uk | ||
| Role | The distributor is the person or organisation that distributes the resource. | distributor |
| Organisation name | Archaeology Data Service | |
| help@archaeologydataservice.ac.uk | ||
| Resource locators | ||
| Locator URL | Web address (URL) that links to the resource | https://doi.org/10.5284/1053114 |
| Locator function | Code that describes the function of the resource. ISO function code chosen from ISO 19115-1 Codelist | download |
| 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 | This states any limitations on access to the data. Multiple occurences are allowed here. One entry shall be from the INSPIRE Metadata registry and the other free text should be part of the resource `Have specific limitations`. | User must agree to ADS conditions https://archaeologydataservice.ac.uk/advice/termsOfUseAndAccess |
| 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. | User must agree to ADS conditions https://archaeologydataservice.ac.uk/advice/termsOfUseAndAccess |
| Available data formats | ||
| Data format | Format in which digital data can be provided for transfer | Documents |
| 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. | 2019-04-23 |
| 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. | 2025-04-23 |
| 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 |