© 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
- How-To
- About
- Contact MEDIN
- Share
Metadata: 2002, Safetec UK Ltd, Gunfleet Sands 1 and 2, Collision Risk Assessment
Abstract:
Enron Wind Gunfleet Ltd. (Enron Wind) have commissioned Safetec UK Ltd (Safetec) to undertake a collision risk assessment of the Gunfleet Sands area. This assessment assists to identify any concerns within the area in order that the proposed wind turbine locations and cable laying / routing can be planned with due regard to minimising the impact upon the environment, and improving working efficiency within the project. The outcomes of the study identified there was a large amount of traffic (10,222 vessels per annum) passing within 10nm of the proposed development area. However, it is noted that approximately 99% of this traffic passes at least 3.7nm from the area of interest, which is considered to be a safe passing distance. This passing traffic is associated with the ports/docks accessed via the Thames such as Tilbury dock, Thames port and Medway port, and due to the nature of their current course these vessels tend to naturally avoid the area of interest as they navigate between the sandbanks and associated shallow waters via the recommended deepwater routes through the Thames Estuary. It is also considered that due to the position of the proposed development area within the Gunfleet Sands, vessels passing on the closed passing route (No.1) will be unaffected by the development as they already navigate to avoid the Gunfleet Sands.
Data holder:
The Crown Estate
| Other details | ||
| Internal code | Internally assigned metadata identifier | 18300 |
| 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. | 2002, Safetec UK Ltd, Gunfleet Sands 1 and 2, Collision Risk Assessment |
| 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. | 0f1b7cc9-6ed6-4456-827b-a99725d60127 |
| Resource Identifier | This is the code assigned by the data owner. | TCE-521 |
| 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 | 2002-02-01 |
| End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2002-02-01 |
| 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. | Enron Wind Gunfleet Ltd. (Enron Wind) have commissioned Safetec UK Ltd (Safetec) to undertake a collision risk assessment of the Gunfleet Sands area. This assessment assists to identify any concerns within the area in order that the proposed wind turbine locations and cable laying / routing can be planned with due regard to minimising the impact upon the environment, and improving working efficiency within the project. The outcomes of the study identified there was a large amount of traffic (10,222 vessels per annum) passing within 10nm of the proposed development area. However, it is noted that approximately 99% of this traffic passes at least 3.7nm from the area of interest, which is considered to be a safe passing distance. This passing traffic is associated with the ports/docks accessed via the Thames such as Tilbury dock, Thames port and Medway port, and due to the nature of their current course these vessels tend to naturally avoid the area of interest as they navigate between the sandbanks and associated shallow waters via the recommended deepwater routes through the Thames Estuary. It is also considered that due to the position of the proposed development area within the Gunfleet Sands, vessels passing on the closed passing route (No.1) will be unaffected by the development as they already navigate to avoid the Gunfleet Sands. |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | Identification of Shipping Pattern will be assessed utilising the COAST database which has been developed by Safetec on behalf of the DETR, HSE and UKOOA. This data source contains details of route positions, traffic volumes and vessel size/type distributions for all merchant shipping routes passing through UK waters. It should be noted that the database does not include details of routes which are termed as non-routine traffic e.g. fishing vessels, traffic to mobile drilling units, etc. Generally the COAST database carries information of all route based traffic that are over 10m in length or 100 GRT (gross registered tonnage). It is also noted that for this study the database has been updated based on survey data recently recorded in the Thames Estuary by Dover CNIS and Port of London Authority. Determination of Collision Frequency was performed using the data contained within the COAST database as input to the COLLIDE 2.60 model. The model developed was also based on site specific environmental and wind turbine tower details. |
| Additional information | This describes relevant references to the data e.g. reports, articles, websites plus other useful information not captured elsewhere. | Presentation type: digital representation of a primarily textual item (can contain illustrations also) Supply media: 002 Origin: Safetec UK Ltd |
| Related keywords | ||
| Keyword | General subject area(s) associated with the resource, uses multiple controlled vocabularies | Hazards to navigation |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Transport activity | |
| 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 | Agreement for Lease Area | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Atmospheric conditions | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Transport networks | |
| Geographical coverage | ||
| North | The northern-most limit of the data resource in decimal degrees | 51.752910014735 |
| East | The eastern-most limit of the data resource in decimal degrees | 1.2609909324585 |
| South | The southern-most limit of the data resource in decimal degrees | 51.710526813632 |
| West | The western-most limit of the data resource in decimal degrees | 1.1822141549296 |
| 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 | Orsted | |
| Position name | Project Manager | |
| info@orsted.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 | Safetec | |
| sales@safetecdirect.co.uk | ||
| 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 | Orsted | |
| info@orsted.com | ||
| Resource locators | ||
| Locator URL | Web address (URL) that links to the resource | https://www.marinedataexchange.co.uk/details/TCE-521/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 |
| Harvest date | The date which this record has been (re)harvested from the provider. | 2026-09-27 |
| Metadata date | The date when the content of this metadata record was last updated. | 2026-09-10 |
| 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 |