Overview

A receptor is any place, feature, or community characteristic that could be materially affected by construction, operations, access, noise, land take, pollution, habitat disruption, or social change.

In practice, receptor mapping often starts with an untidy mix of schools, clinics, settlements, protected areas, rivers, religious sites, and community assets. The method is not just to collect them. It is to classify them in a way that supports defensible screening.

Why it matters

Classification matters because not all features should carry the same analytical weight. A protected wetland, a primary school, and a seasonal drainage line may all matter, but not in the same way and not at the same stage of decision-making.

Without classification, maps become visually dense but analytically weak.

When to use

Use this method when:

• screening candidate sites or route options
• building an environmental and social baseline
• preparing field verification priorities
• briefing non-specialists on what spatial constraints deserve attention

Inputs

• settlement and place layers
• public-service points such as schools and clinics
• hydrology and water features
• protected areas and biodiversity-related boundaries
• project footprint, corridor, or buffer geometry
• local context notes on which receptors are known to be under-mapped

Receptor classes

Live receptor classification example

Workflow and method

1. Assemble candidate receptors from multiple open layers.
2. Standardize them into a small number of receptor classes.
3. Flag confidence levels where the source is weak or inferred.
4. Review overlaps and possible duplicates.
5. Screen against the project footprint or buffer.
6. Produce separate outputs for analytical review and field verification.

Example screening logic

One practical early-stage logic is:

• High attention: schools, hospitals, protected areas, large settlements, permanent rivers
• Medium attention: clinics, water points, residential polygons, secondary schools, wetlands
• Watch list: small hamlets, seasonal drainage, isolated buildings, inferred settlement clusters

This is not universal. It is a starting pattern that should be adjusted by sector, country context, and the likely project impact pathway.

Tools and query patterns

Typical acquisition patterns include:

• Overpass queries for public-service and settlement-related features
• protected-area reference datasets from national or global sources
• hydrology layers from open reference data or existing project baselines
• manual review of imagery where settlement data is clearly incomplete

Illustrative classification fields:

receptor_id
receptor_class
receptor_subclass
source_name
source_system
confidence_level
screening_priority
notes

Outputs

Expected outputs include:

• a clean receptor layer with stable classes
• a summary table by class and priority
• a field-verification shortlist
• a map that clearly separates social and environmental receptors

Data limitations

• OSM public-service tagging is uneven across regions.
• Settlement representation may be fragmented between place points and residential landuse polygons.
• Protected-area boundaries can vary by source and update cycle.
• Water features are often incomplete in flat, remote, or seasonally dynamic landscapes.

Limitations

This method helps structure the baseline, but it does not remove the need for local knowledge. Some receptors are socially important and almost invisible in open datasets. Others appear in the data but have low real-world sensitivity for a given project decision.