How LandLens Verifies Flood Zone Data Using True Geometric Analysis

If you use any planning intelligence tool to check flood risk on a development site, there is a question you should be asking: how does it actually determine whether a postcode falls inside a flood zone?

The answer matters more than you might think. The difference between a correct methodology and a shortcut can mean the difference between a site flagged as Flood Zone 3 and a site correctly identified as Zone 1 — which has direct implications for insurance, planning viability, and acquisition decisions.

This post explains the methodology LandLens uses, why it goes beyond the standard approach, and what it means for site assessments run on the platform.

The Data Source: Environment Agency Flood Map for Planning

LandLens queries the Environment Agency's Flood Map for Planning dataset, delivered via a Web Feature Service (WFS). This is the same dataset used in formal flood risk assessments and referenced by planning authorities across England. It contains polygon geometries representing Flood Zone 2, Flood Zone 3, and functional floodplain boundaries.

When you search a postcode on LandLens, the platform converts that postcode to a coordinate and queries the EA WFS for flood zone polygons in the vicinity.

The Problem With Bounding-Box Matching

Here is where methodology matters. The EA WFS, like most spatial data services, supports a bounding box filter — a rectangular window around the query point. The service returns any feature whose own bounding box overlaps with that query window.

The critical detail: a polygon's bounding box is not the same as its actual geometry. A flood zone polygon that follows a narrow river corridor might have a bounding box extending hundreds of metres in every direction. If your tool simply checks whether the EA returned any features, without verifying the actual geometry, it will report false positives.

Consider a postcode 130 metres from a river. The river's flood zone polygon exists nearby, and its bounding box easily overlaps the query window. A bounding-box-only tool marks that postcode as Flood Zone 3. But the actual flood zone boundary is nowhere near the postcode.

This is not a theoretical problem. During internal testing, we identified postcodes being flagged as Flood Zone 3 where the nearest actual flood zone boundary was over 300 metres away.

How LandLens Does It Differently

LandLens uses a three-step verification process that goes beyond bounding-box overlap:

Step 1 — Controlled Query Window

The initial WFS query uses a spatial window calibrated to be generous enough to catch postcodes near flood zone boundaries, while keeping the number of candidate polygons manageable. This is the pre-filter — it retrieves potential matches, not confirmed ones.

Step 2 — Coordinate System Alignment

The EA WFS defaults to British National Grid (EPSG:27700) coordinates. Postcode coordinates from geocoding services are in WGS84 (EPSG:4326). Before any geometric comparison, LandLens forces explicit coordinate system alignment to ensure the point and polygon coordinates are in the same reference frame. A mismatch here — even a small one — can shift comparisons by tens of metres.

Step 3 — True Point-in-Polygon Verification

This is the key step. Every flood zone polygon returned by the WFS is tested geometrically to confirm whether the postcode coordinate actually falls inside it. Not whether the bounding boxes overlap. Not whether the polygon is "nearby." Whether the point is contained within the polygon boundary.

Only polygons that pass this test are counted as a confirmed match. If a flood zone polygon is returned by the WFS but does not geometrically contain the postcode coordinate, it is discarded.

Verification Across Test Cases

The methodology was validated against a range of test postcodes — both postcodes that should return no flood zone classification, and known flood-prone locations that should:

The rural postcodes in the first three rows are the type most likely to be misclassified by tools using bounding-box-only matching — close to a river, but not actually inside a flood zone. The urban flood-prone locations in the last three rows confirm that the verification does not produce false negatives.

Where This Applies on LandLens

This verification methodology is applied across every route on the platform that queries flood zone data:

• Constraint Map — the flood risk check you see when you search any postcode
• Bulk Postcode Search — flood checks across batches of up to 50 postcodes
• AI Site Reports — the flood data referenced in generated PDF reports

The same three-step process runs every time. There are no shortcuts for bulk queries or report generation.

Why This Matters for Due Diligence

Flood zone classification directly affects:

• Planning viability — development in Flood Zone 3 triggers the Sequential Test and Exception Test under NPPF
• Insurance costs — Flood Re eligibility and commercial flood insurance premiums are zone-dependent
• Lender requirements — mortgage lenders routinely decline or impose conditions on Zone 3 properties
• Site acquisition pricing — an incorrect flood zone flag can artificially suppress a site's perceived value

If your pre-acquisition screening tool tells you a site is in Flood Zone 3 when it is not, that is not just an inaccuracy — it can cost real money in abandoned opportunities or unnecessary flood risk assessments.

Transparency as Standard

We are publishing this because we believe planning professionals deserve to understand the methodology behind the data they rely on. Every constraint check on LandLens — flood risk, conservation areas, listed buildings, green belt, Article 4 — uses the best available government data sources and verifiable processing logic.

If you have questions about how any specific constraint is checked, or want us to verify a particular postcode result, contact us at [email protected].

Vince James is the founder of LandLens™, a UK AI planning intelligence platform that gives property professionals instant access to planning constraint data for any UK postcode.