Skip to main content

Listed Buildings

What it is

Listed Buildings are buildings and structures of special architectural or historic interest, protected under the Planning (Listed Buildings and Conservation Areas) Act 1990, and held on the National Heritage List for England (NHLE) by Historic England. They are graded:

  • Grade I — exceptional interest.
  • Grade II* — particularly important, more than special interest.
  • Grade II — special interest (the large majority).

How it's produced

Compiled and maintained by Historic England as part of the NHLE and published as open data. The NHLE actually publishes listed buildings as both a point layer and a building-footprint polygon layer. WildStack's own ingested table uses the point layer only — the claims below about point-only geometry describe WildStack's constraint_listed_buildings table specifically, not the NHLE export as a whole.

Update frequency & currency

Continuously maintained as buildings are listed, amended, or delisted.

Spatial resolution / precision

A critical handling note: WildStack ingests the NHLE's point layer for listed buildings — a marker at each building's location, not its outline (NHLE also publishes a separate polygon layer, not currently used in this pipeline). This has a hard engineering consequence for the ingested table:

Engineering gotcha

Because WildStack's constraint_listed_buildings table is points (a MULTIPOINT layer), area must never be calculated from itST_Area() on a point is meaningless. Spatial work uses intersection/proximity only. This is an explicit rule for this table, not a general property of the NHLE listed-buildings dataset.

Known limitations

  • Point location, not footprint, in WildStack's ingested table. NHLE also publishes a polygon layer, but WildStack ingests the point layer, whose marker doesn't delineate the building's extent or curtilage.
  • Curtilage complexity. Protection can extend to structures within a listed building's curtilage that aren't separately marked.
  • Heritage, not ecology. A planning constraint, not habitat evidence.

How it compares to Scheduled Monuments

Same publisher and source list, different regime, and a different geometry choice in WildStack's own pipeline — see the comparison table on the Scheduled Monuments profile. One line: Scheduled Monuments are polygons under the 1979 Act; WildStack ingests Listed Buildings as points under the 1990 Act (NHLE also publishes a polygon layer for Listed Buildings, not currently used here).

Role in BNG assessment

Briefing-pack context only in WildStack's stack — listed buildings inform the planning narrative but do not fire a BNG trigger and never contribute habitat parcels. They are handled by intersection/proximity only, never by area.

WildStack's take

Listed buildings are the textbook example of why geometry type is a data-literacy issue, not a technicality. They look like just another "heritage points" layer, but the point-versus-polygon distinction versus Scheduled Monuments is exactly what trips up naive spatial analysis — try to compute an area or a proper overlap from points and you get nonsense, silently. We treat the geometry type as a first-class fact about the dataset. On the planning side, the honest framing is the same as for any heritage layer: flag it, hand it to a heritage specialist, and don't let it distort the ecological assessment it has nothing to do with.

Official source

Last reviewed

5 July 2026. Revisit if the NHLE data distribution, the geometry representation, or the listing framework changes.