Showing Wirral search areas — postcode distances are measured to these.
Inside thesearch area
Toggle to see what lies inside the corridor near you.
Indicative scoping boundary
Applicant-published mapping available through the Planning Inspectorate (PINS) project record
Not used for postcode distance — context onlyMust not be read asconfirmed route, construction boundary, land-take, hazard zone or safety zone
A confirmed route, working areas, access routes and land-take are not shown in the current applicant material used for this map.
Wirral consultation polygons (Sections 9–10)
Applicant-published consultation mapping — Peak_Cluster_AGOL_Individual_Sections FeatureServer/13 (Section 9) and FeatureServer/12 (Section 10). Copyright: Arup/AECOM.
Used for postcode distanceMust not be read asconfirmed route, final alignment, land-take, works boundary, hazard zone or safety zone
Cheshire West sections (Sections 7–8)
Applicant-published section polygons — Peak_Cluster_AGOL_Individual_Sections FeatureServer/15 (Section 7: Tarporley to Picton) and FeatureServer/14 (Section 8: Picton to Willaston, including Connection AGIs 2 and 3 in Ellesmere Port). Copyright: Arup/AECOM. Last edit: 24 October 2025. Both sections lie within Cheshire West and Chester (CWaC). This tool focuses on Wirral and Cheshire West sections. Section 6 is not shown.
Not used for postcode distance — context onlyMust not be read asconfirmed route, final alignment, land-take, works boundary, hazard zone or safety zone
The coloured section is not the final pipe route. It shows Peak's current published search areas, within which route options are still being developed. A confirmed route, working width, access routes and land-take are not shown in the current applicant material used for this map.
Coastal facility search areas
Applicant-published Coastal facility search areas — Peak_Cluster_AGOL_Coastal_AGI FeatureServer/10 (Landfall zone) and FeatureServer/11 (Inland zone).
Used for postcode distanceMust not be read asfinal Coastal facility site, final land boundary, construction compound, safety zone or hazard zone
Cement/lime source-site markers
Peak Cluster applicant material identifies the named cement and lime source sites. Marker positions are approximate — derived from each site's postcode via postcodes.io, which returns the postcode's central point, not the plant's actual location. They are not exact plant boundaries, capture points, route points or distance layers.
Not used for postcode distance — context onlyMust not be read asexact plant boundary, capture point, route point, confirmed facility location, safety zone or hazard zone
Visible only on the Full Project map.
Eastern sections (1–6)
Applicant-published section polygons for the eastern half of the corridor through Cheshire East and Derbyshire — Peak_Cluster_AGOL_Individual_Sections (Sections 1–6). Copyright: Arup/AECOM.
Not used for postcode distance — context onlyMust not be read asconfirmed route, final alignment, land-take, works boundary, hazard zone or safety zone
Visible only on the Full Project map.
Proposed CO₂ storage area (Morecambe)
According to the applicant’s Project Guide (January 2026), Peak Cluster would transfer captured CO₂ to Morecambe Net Zero, operated by Spirit Energy, for storage in the “depleted South and North Morecambe gas fields” beneath the East Irish seabed. The four indicative outlines shown on the map sit over the offshore licensing area where those depleted fields lie. They are illustrative shapes, not the operator-determined field outlines (which are maintained by the North Sea Transition Authority and were not reachable at build time).
Not used for postcode distance — context onlyMust not be read asthe exact field outline, the confirmed storage extent, a confirmed subsea pipeline route, or evidence that storage is “into the sea”. The proposed store is geological — in depleted gas reservoirs beneath the seabed.
Visible only on the Full Project map. Dashed outlines + on-map callout signal that these are indicative shapes, not exact field boundaries.
Habitats (woodland, scrub, heath, grassland, wetland)
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for natural=wood/scrub/heath/grassland and similar habitat tags within the corridor bbox, clipped to applicant section polygons. Built by scripts/build-habitat-layers.mjs.
Must not be read asa complete habitat survey, an authoritative biodiversity assessment, or a substitute for the applicant’s required ecological assessments
Farmland
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for landuse=farmland/meadow/orchard within the corridor bbox.
Must not be read asa complete agricultural-land map or a substitute for the applicant’s required land-use assessment
Waterways (rivers, canals, streams, drains, ditches)
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for waterway tags within the corridor bbox. Excludes culverted and buried sections via tunnel filter; open drainage ditches are included as wildlife corridors. Built by scripts/build-water-layers.mjs.
Not used for postcode distance — context onlyMust not be read asa complete hydrological inventory, an Environment Agency authoritative dataset, or a substitute for the applicant’s required water-environment assessment
Water bodies
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for natural=water polygons within the corridor bbox. Includes ponds, lakes and reservoirs that fall within applicant section polygons.
Must not be read asa complete surface-water inventory or flood-zone mapping
Transport (roads and railways)
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for major roads (highway=motorway/trunk/primary/secondary/tertiary/unclassified, named residential roads, and tracks) and railways (railway=rail/light_rail) within the corridor bbox. Clipped to applicant section polygons. Built by scripts/build-transport-layers.mjs.
Must not be read asa complete construction-disruption map, a road-closure plan, or a transport-impact assessment
Paths & cycleways
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for path-like infrastructure (highway=footway/path/bridleway/cycleway/track/steps), ways carrying a public-right-of-way designation tag (public_footpath/bridleway/byway/restricted_byway), and member ways of named long-distance foot/hiking route relations and National/Regional Cycle Network (NCN/RCN) relations. Built by scripts/build-active-routes.mjs.
Must not be read asan authoritative Public Rights of Way record, a legal access map, or a substitute for the Definitive Map maintained by the local highway authority. OSM designation tags are crowd-sourced and may be incomplete or out of date; many physical paths in OSM are not tagged with their legal status.
Receptors (schools and care homes)
OpenStreetMap contributors, ODbL 1.0. Built from Overpass API queries for schools (amenity=school/kindergarten/childcare) and care homes (amenity=social_facility/nursing_home) within 1.5 km of the indicative scoping boundary. Built by scripts/build-receptor-layers.mjs.
Must not be read asan authoritative schools or care-home register, a substitute for Department for Education or CQC published data, or a complete vulnerable-receptor inventory
Postcode distances are approximate. They are measured from the approximate centre of the postcode to the current published Wirral search area polygons and Coastal facility search areas. They are not measured to a confirmed route, final Coastal facility site, exact address, safety zone or hazard boundary. The postcode lookup sends the postcode to postcodes.io to retrieve approximate coordinates. This site does not store the postcode.
The current applicant material used for this map does not show a confirmed pipeline route, final Coastal facility site, final construction boundary or property-level impact assessment. This map is therefore a proximity and interpretation tool, not a final impact map. This is not legal, planning, safety or land advice, and it is not an official map from the Planning Inspectorate, Wirral Council or any regulator.
According to applicant-published material, the Coastal Above Ground Installation (AGI) would be above-ground infrastructure close to the Wirral North Shore. The exact location is still being developed. The applicant says it would compress CO₂ before onward transport to the Morecambe Net Zero store, and would monitor and meter the flow.
According to applicant-published material:
Unlike the buried pipeline, the AGI would be permanent above-ground infrastructure on the Wirral coast. Until the site, layout and operating assumptions are published, residents cannot properly assess local effects.
This map shows applicant-published mapping for the Peak Cluster proposal — the indicative scoping boundary, Wirral search-area polygons and Coastal facility search areas — combined with contextual overlays from OpenStreetMap (transport, paths, waterways, habitats, farmland, receptors). Full layer attribution is in Sources & method.
It does not show a confirmed pipeline route, a final Coastal facility site, a construction boundary, a safety or hazard zone, or property-level impacts.
Postcode distances are approximate. They are measured from the approximate centre of the postcode area to the current published Wirral search area polygons and Coastal facility search areas, not to a confirmed route or exact address.
Sources: Peak_Cluster_AGOL_Individual_Sections FeatureServer/12–13 (Wirral sections 9–10); FeatureServer/14–15 (Cheshire West sections 7–8); Peak_Cluster_AGOL_Coastal_AGI FeatureServer/10–11 (AGI zones). Applicant-published, Arup/AECOM. Overlay layers: OpenStreetMap contributors, ODbL 1.0.
According to applicant-published material, Peak Cluster would carry captured CO₂ from cement and lime plants in Derbyshire and Staffordshire across Cheshire and the Wirral to a possible coastal surface facility close to the Wirral North Shore, then onward for proposed offshore storage through Morecambe Net Zero beneath the East Irish Sea.
This is a conceptual journey summary based on applicant-published material. It is not a confirmed route, final site or safety zone.
Source: Peak Cluster Project Guide (January 2026) and Above Ground Infrastructure factsheet (March 2026) — applicant-published.
Three approximate markers are shown because Tarmac Tunstead and Buxton Lime Tunstead share one Tunstead location. Click a marker for details. Not used for postcode distance calculations.
Markers show approximate postcode-area centres — not exact plant boundaries or capture points.