Overview
The conservation-screening examples in the sibling workspace point toward a consistent method: combine formal protected-area layers with habitat-priority and biodiversity-significance layers, then review them against the project footprint in a way that preserves uncertainty.
The strongest source material comes from:
- WDPA and KBA mapping experiments
- Berkshire conservation-screening examples
- mixed screening maps that use multiple ecological layers together rather than one headline polygon
Why it matters
- Legal protection status is only part of the ecological picture.
- A site outside a protected boundary may still intersect habitat priorities, wetland systems, or biodiversity trigger areas.
- Early visibility on this helps avoid weak route choices hardening into preferred options.
When to use
Use this method when:
- screening candidate sites, corridors, or access routes
- preparing a desktop biodiversity baseline
- framing specialist follow-up scope
- assembling lender or stakeholder screening materials
Inputs
- WDPA and national protected-area layers
- KBA or similar biodiversity-priority layers
- wetlands, water features, forest cover, or habitat proxies
- project footprint, corridor, buffers, and crossings
Workflow and method
- Load source layers separately rather than dissolving them too early.
- Classify them by analytical role: formal protection, biodiversity priority, habitat context, and hydrology.
- Screen direct overlap first.
- Screen proximity and corridor adjacency next.
- Flag data-confidence issues and likely under-mapped areas.
- Produce a shortlist for specialist review and field verification.
Example screening logic
| Screening band | Typical condition | Example implication |
|---|---|---|
| High concern | Direct overlap with protected area or KBA | Avoid, reroute, or escalate quickly |
| Elevated concern | Within buffer of protected, wetland, or habitat-priority features | Needs closer review and justification |
| Context watch | Nearby ecological features without direct overlap | Keep visible in route refinement and field prep |
Live conservation stack example
Tools and query patterns
Useful implementation patterns drawn from the sibling projects:
- map protected and biodiversity layers separately in the web map
- use different fills and line treatments rather than one merged color
- expose enough attributes in popups or tables to support manual review
- keep fast global context layers separate from detailed feature queries
Outputs
Expected outputs:
- a screening map with distinct conservation layer families
- overlap and proximity summary tables
- notes on likely specialist triggers
- a list of places requiring field confirmation or better source data
Limitations
- Conservation layers differ in legal effect and should not be conflated.
- Habitat proxies are useful but imperfect.
- Global layers can lag national updates.
- Some ecologically important areas are poorly represented in open data.