© 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: 2012, Renewable Energy Systems Ltd, Zone 9 Celtic Array, Preliminary Aviation Assessment
Abstract:
This assessment was prepared by Renewable Energy Systems Ltd (“RES”). and the report presents an assessment of the Round 3 Offshore Irish Sea Zone and the potential impact that the projects may have on nearby aviation facilities like the on Ministry of Defence , NERL and the Isle of Man airport infrastructure The proposed Round 3 Offshore Irish Sea zone is situated off the west coast of England and south east of the Isle of Man. Due to the large extent of the area a zonal approach was undertaken to assess the potential environmental impacts. The majority of sites lie beneath controlled airspace corridors including the south eastern extent of the Isle of Man CTA1, L10, L70 & L90. The nearest aerodrome is the Isle of Man airport which is approximately 27km (14.5nm) to the edge of the nearest site; there are additionally a number of heliports on the eastern side of the project mainly concentrated around the Morecambe gas field. Available dataset : GIS outputs- MXD and Shapefiles; Drawings and Reports in PDF Corresponding Centrica Document No: R3-D-EN-130-0000-000000-001
Data holder:
The Crown Estate
| Other details | ||
| Internal code | Internally assigned metadata identifier | 36306 |
| 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, Renewable Energy Systems Ltd, Zone 9 Celtic Array, Preliminary Aviation 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. | 58418da5-48ee-4f6c-a0cb-193482b0d459 |
| Resource Identifier | This is the code assigned by the data owner. | TCE-2680 |
| 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-12-31 |
| 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'. | weekly |
| Abstract | The abstract provides a clear and brief statement of the content of the resource. | This assessment was prepared by Renewable Energy Systems Ltd (“RES”). and the report presents an assessment of the Round 3 Offshore Irish Sea Zone and the potential impact that the projects may have on nearby aviation facilities like the on Ministry of Defence , NERL and the Isle of Man airport infrastructure The proposed Round 3 Offshore Irish Sea zone is situated off the west coast of England and south east of the Isle of Man. Due to the large extent of the area a zonal approach was undertaken to assess the potential environmental impacts. The majority of sites lie beneath controlled airspace corridors including the south eastern extent of the Isle of Man CTA1, L10, L70 & L90. The nearest aerodrome is the Isle of Man airport which is approximately 27km (14.5nm) to the edge of the nearest site; there are additionally a number of heliports on the eastern side of the project mainly concentrated around the Morecambe gas field. Available dataset : GIS outputs- MXD and Shapefiles; Drawings and Reports in PDF Corresponding Centrica Document No: R3-D-EN-130-0000-000000-001 |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | For the Radar Model - Propagation , the radar model used to determine the magnitude of a wind turbines return to a primary radar system is based on ITU recommendations and is in accordance with the CAA’s (Civil Aviation Authority) assessment methodology for determining the impact of wind turbines on aeronautical radar systems. The ITU (International Telecommunication Union) is the body that provides recommendations and guidelines to regulate and protect telecommunications. The calculation of a wind turbines radar cross section (RCS) was complicated due to the complex blade shape, rotation of blades and the varying pitch and orientation of the blades with respect to the incident electromagnetic waves. It is not related just to the physical size of an object but also to material properties, frequency and other factors. A number of attempts was made to model the RCS of a wind turbine, despite this there was still a great deal of uncertainty with defining a fixed RCS value to a turbine. |
| Related keywords | ||
| Keyword | 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 | Radar backscatter | |
| 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 | Transport networks | |
| 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 | Celtic Array | |
| Position name | GIS and Data Manager | |
| info@celticarray.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 | Renewable Energy Systems Ltd | |
| Position name | Project Manager | |
| info@res-ltd.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 | |
| unknown | ||
| Resource locators | ||
| Locator URL | Web address (URL) that links to the resource | https://www.marinedataexchange.co.uk/details/TCE-2680/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 | |
| 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`. | Distribution by Celtic Array Ltd on a case by case basis | |
| 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 |
| 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. | Distribution by Celtic Array Ltd on a case by case basis | |
| 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. | 2014-09-01 |
| Harvest date | The date which this record has been (re)harvested from the provider. | 2026-04-17 |
| Metadata date | The date when the content of this metadata record was last updated. | 2026-04-16 |
| 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 |