Planning data for GIS
Put planning activity on your own map.
Run coordinate radius searches for mapped applications, return distance from the query point, and retain source, freshness and identity fields for inspection panels and spatial workflows.
Product and property teams use PlanWire when they need source-linked planning data without maintaining council-source integrations, with UPRN where available for property-dataset joins. Source-linked application records, freshness metadata and webhook workflows. Check current council-level coverage and history for your integration.
Search within one kilometre
Use coordinates, not a postcode, on the nearby endpoint. Paid plans support larger radii than evaluation keys within published limits.
GET /v1/applications/nearby?lat=51.5074&lng=-0.1278&radius_km=1&limit=50 X-API-Key: YOUR_API_KEY
A spatial search layer for your product.
The endpoint searches records with usable coordinates. Applications without location geometry cannot appear in radius results and must remain a visible coverage limitation.
Search a coordinate
Send WGS84 latitude and longitude with a radius in kilometres to retrieve the nearest captured applications inside the boundary.
Use distance fields
Nearby responses include distance_m so a map, list or triage rule can order results around the query point.
Join property identity
Use UPRN and match provenance where available to connect mapped planning activity to internal assets and property datasets.
Show evidence state
Display council references, source URLs and freshness metadata rather than presenting every marker as a current official determination.
Spatial result boundaries
| Included | Captured applications with stored location geometry inside the requested coordinate radius. |
|---|---|
| Not included | Records without usable coordinates, even if their text address might be close to the search point. |
| Verification | The result retains the authority reference and source link for detailed inspection. |
Questions buyers ask
Can I search a polygon?
The documented PlanWire nearby endpoint uses a coordinate and radius. Do not assume polygon search is available unless it appears in the current API documentation.
Does every application appear on the map?
No. Radius results require usable location geometry, and location fields are not available on every source record.
Can I use the results in a GIS product?
Yes, subject to plan limits and the published data-use terms for your display, caching and redistribution model.
Related acquisition pages