© 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, Zone 9 Celtic Array, Zonal Appraisal and Planning (ZAP) Report
Abstract:
In order to better understand the issues developers faced in previous leasing rounds for offshore wind, CERI (now Celtic Array) adopted a new zonal approach to offshore wind development, as advocated by The Crown Estate (2010). This approach, termed Zone Appraisal and Planning (ZAP), a two year process and is a voluntary basement with no legal requirements. It aimed to identify areas within the ISZ that are on balance more ‘developable’ based on human, environmental, technical and commercial considerations. It also allowed CERI the opportunity to understand the nature of the zone and to manage the consenting risks at a zone-wide level, particularly in terms of cumulative and incombination effects and obligations under the Round 3 Plan-level Habitats Regulations Assessment, undertaken by The Crown Estate in 2010 (The Crown Estate 2010). The intention is then to identify potential sites in the ISZ that will be brought forward and assessed as part of the statutory EIA phase. This ZAP will add significant value to the long-term identification, and subsequent building, of projects should they be successful at the consenting stage. Associated Document :R3-D-EV-001-0000-000000-031
Data holder:
The Crown Estate
| Other details | ||
| Internal code | Internally assigned metadata identifier | 19356 |
| 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, Zone 9 Celtic Array, Zonal Appraisal and Planning (ZAP) Report |
| 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. | b148dfd5-6a8b-44c2-b38e-6d785180c47e |
| Resource Identifier | This is the code assigned by the data owner. | TCE-2692 |
| 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-07-11 |
| End date | This describes the date the resource ends. This may only be the year if month and day are not known | 2012-07-11 |
| 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. | In order to better understand the issues developers faced in previous leasing rounds for offshore wind, CERI (now Celtic Array) adopted a new zonal approach to offshore wind development, as advocated by The Crown Estate (2010). This approach, termed Zone Appraisal and Planning (ZAP), a two year process and is a voluntary basement with no legal requirements. It aimed to identify areas within the ISZ that are on balance more ‘developable’ based on human, environmental, technical and commercial considerations. It also allowed CERI the opportunity to understand the nature of the zone and to manage the consenting risks at a zone-wide level, particularly in terms of cumulative and incombination effects and obligations under the Round 3 Plan-level Habitats Regulations Assessment, undertaken by The Crown Estate in 2010 (The Crown Estate 2010). The intention is then to identify potential sites in the ISZ that will be brought forward and assessed as part of the statutory EIA phase. This ZAP will add significant value to the long-term identification, and subsequent building, of projects should they be successful at the consenting stage. Associated Document :R3-D-EV-001-0000-000000-031 |
| Lineage | Lineage includes the background information, history of the sources of data, data quality statements and methods. | ZAP is not a planning application. ZAP is a non-statutory strategic programme of data collection, consultation and assessment which has identified three areas of search which may host offshore wind farms. In any case, each offshore wind farm will be subject to EIA and public consultation and will be examined by the IPC (or its successor) prior to any decision from the Department of Energy and Climate Change. There is no legal requirement to undertake ZAP. It is a process CERIcarried out voluntarily because it believes that ZAP will add significant value to the long-term identification, and subsequent construction, of the proposed projects Stakeholder consultation was undertaken throughout the entire ZAP process. |
| Related keywords | ||
| Keyword | General subject area(s) associated with the resource, uses multiple controlled vocabularies | Bird counts |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Fish taxonomy-related counts | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Bird behaviour | |
| 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 | Acoustic noise in the water column | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Cetacean behaviour | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Marine archaeology | |
| 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 | Seal behaviour | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Fishery characterisation | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Seal abundance | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Fish abundance in water bodies | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Cetacean abundance | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Sediment grain size parameters | |
| 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 | Habitat characterisation | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Sea level | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Horizontal velocity of the water column (currents) | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Salinity of the water column | |
| 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 | Land cover | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Habitats and biotopes | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Population distribution - demography | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Hydrography | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Meteorological geographical features | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Land use | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Geology | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Oceanographic geographical features | |
| General subject area(s) associated with the resource, uses multiple controlled vocabularies | Species distribution | |
| 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 | Centrica Energy Renewable Investments (CERI) | |
| Position name | GIS and Data Manager | |
| CERI@centrica.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 | The Crown Estate | |
| mde@thecrownestate.co.uk | ||
| Resource locators | ||
| Locator URL | Web address (URL) that links to the resource | https://www.marinedataexchange.co.uk/details/TCE-2692/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. | 2009-05-01 |
| Harvest date | The date which this record has been (re)harvested from the provider. | 2026-04-19 |
| Metadata date | The date when the content of this metadata record was last updated. | 2026-04-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 |