Vepler logo
Live
Planning & Development
New

Article 4 Directions

17,666 Article 4 direction extents across England, each a mappable polygon carrying the permitted-development rights it removes, built from the national platform, council GIS and order documents.

17,666
Article 4 extents
10,707
Off the national platform
11 Jul 2026
Refreshed
Overview

About this dataset

An Article 4 direction is how a local planning authority removes permitted-development rights over a defined area, so works that would normally be automatic (an extension, new cladding, replacement windows, an HMO conversion, a demolition) instead need a planning application. This dataset holds 17,666 of those extents across England, each a full EPSG:4326 polygon ready to map and run point-in-polygon checks against.

Only about a third of England's planning authorities have published their Article 4 boundaries to the national data platform, and the platform itself warns its coverage is incomplete. The rest are made authority by authority and live in council GIS services, order documents and scanned maps. We build the missing majority. 6,959 extents come straight from the national platform; we resolve the other 10,707 ourselves, by reading council endpoints, matching directions to their conservation-area boundaries, geocoding enumerated property schedules, and tracing order-document maps where nothing else exists. Every extent records how its geometry was derived and how confident that derivation is.

Where the source provides them, each extent carries the GPDO class codes it removes, so you can tell an agricultural-land direction from one that controls shopfronts or house extensions. Every record is stamped with its resolver tier, source URL and licence. The national tier and most council sources are Open Government Licence v3.0; a minority of councils publish under their own terms, which are flagged per record and kept out of commercial redistribution.

Coverage is England only. The General Permitted Development Order is England-specific, and devolved equivalents are separate instruments. Use it for planning constraint checks, site due diligence and mortgage screening, alongside conservation areas, listed buildings and other planning constraints in the same model.

What's included

Everything in the box

The polygons that aren't on the platform

About two-thirds of England's planning authorities haven't published their Article 4 boundaries to the national platform. We resolve those directions from council GIS, conservation-area boundaries, enumerated property schedules and order-document maps.

The rights each direction removes

Every extent carries its GPDO class codes where the source provides them, so a direction over agricultural land reads differently from one controlling shopfronts or house extensions.

Provenance on every extent

Each record is stamped with the resolver tier, source URL and licence behind its geometry, so you can see whether a boundary came from a council endpoint or a traced order map.

Data fields

What each record carries

schema14 fields
reference: string// Stable identifier for the direction extent. For national-tier records this is the MHCLG entity id.
name: string// Name of the Article 4 direction or the area it covers.
nation: enum// UK nation. Always ENG — the dataset is England only.
designation_type: enum// Designation family. Always article_4_direction_area.
designated_date: date// Date the direction took effect, where the source records it.
local_authority: string// Local planning authority that made the direction. Null for national-tier records, which carry the authority as an organisation id in metadata.
area_hectares: float// Polygon area in hectares.
permitted_development_rights: string// GPDO class codes the direction removes, where the source provides them (semicolon-separated).
geometry: object// Full boundary polygon in EPSG:4326 (GeoJSON). Most are the source's own boundary; some are derived (see resolver_tier).
centroid: object// Polygon centroid as EPSG:4326 lat/lng.
resolver_tier: enum// How the geometry was derived: national, gis_endpoint, gis_file, ca_coterminous, enumerated_schedule, pdf_vector or pdf_raster. Marks the provenance and confidence of each extent.
source_url: string// Link to the council page or order document the extent was built from, where available.
licence: string// Licence the source publishes the extent under.
attribution: string// Attribution string to display with the extent.
Use cases

What people build with it

01

Planning constraint checks

Screen an application site for Article 4 directions that remove permitted-development rights and force a full planning application.

Planners
02

Site due diligence

Check whether a site sits inside an Article 4 area before acquisition or design, using the polygon boundary and the specific GPDO rights removed rather than a single point.

Developers
03

Mortgage and valuation risk

Flag properties where permitted-development rights are restricted, which can shape what an owner may change and affect value and saleability.

Lenders
04

Constraint layers in proptech

Add Article 4 boundaries as a map layer or constraint check inside a property platform, with per-record provenance across every source.

PropTech

Frequently asked questions