# England Brownfield Development Opportunity Change Signals (`starshaped_bullsnake/england-brownfield-development-opportunity-change-signals`) Actor

Detect meaningful changes in the official England Planning Data Brownfield Land dataset since the previous run.

- **URL**: https://apify.com/starshaped\_bullsnake/england-brownfield-development-opportunity-change-signals.md
- **Developed by:** [Starshape Tools](https://apify.com/starshaped_bullsnake) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 england brownfield change signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## England Brownfield Development Opportunity Change Signals

Detect what changed since your previous run in the official England Planning Data Brownfield Land dataset.

### What this Actor does

It builds a full current state for brownfield sites in England, keyed by the official Planning Data entity ID, joins the official organisation catalogue for local-authority names, and compares it with the last successful snapshot. It is designed for development, planning, land, housing, investment-research, and public-sector data teams.

Signals: `NEW_BROWNFIELD_SITE`, `SITE_REMOVED`, `PLANNING_PERMISSION_CHANGED`, `SITE_PERMISSIONED`, `OWNERSHIP_STATUS_CHANGED`, `DWELLING_CAPACITY_INCREASED`, `DWELLING_CAPACITY_DECREASED`, `SITE_AREA_CHANGED`, `PERMISSION_TYPE_CHANGED`, `SITE_NAME_CHANGED`, and `END_DATE_CHANGED`. Opportunity-oriented signals explain permission, ownership, and dwelling-capacity changes without claiming approval or commercial outcome. Capacity changes require valid numeric values on both sides and include absolute and percentage deltas where meaningful.

### Official source, licence, and attribution

Source: the official [Planning Data Brownfield Land dataset](https://www.planning.data.gov.uk/dataset/brownfield-land) and Planning Data API, covering England. Licence: Open Government Licence v3.0. Attribution: **© Crown copyright and database right; licensed under the Open Government Licence v3.0. Source: Planning Data, Ministry of Housing, Communities and Local Government.** Commercial reuse, persistent storage needed for comparisons, and derived signals are permitted subject to the OGL conditions.

Planning Data collects authoritative provider data and refreshes its platform frequently; source authorities update registers on their own schedules. Weekly scheduling is a practical default, or daily when prompt detection matters.

### Baseline and input

The first live run validates and stores all England sites and emits zero signals. An unchanged rerun emits zero. `maxItems` limits Dataset output only. Filters support signal type, local authority, postcode prefix, permission status, ownership status, and minimum capacity increase/decrease.

```json
{"mode":"live","signalTypes":["SITE_PERMISSIONED","DWELLING_CAPACITY_INCREASED"],"minDwellingIncrease":10,"maxItems":100}
```

```json
{"signalType":"DWELLING_CAPACITY_INCREASED","entityId":"1700000","siteReference":"BFR001","siteName":"Example site","localAuthority":"Example Council","previousValue":50,"currentValue":80,"absoluteDelta":30,"percentageDelta":60}
```

Use `{"mode":"sample"}` for ADWIC-friendly synthetic changes processed by the production diff engine without accessing or changing the live baseline.

### Safety, storage, and limitations

The order is fetch, parse, normalize/join, validate, load/compare, Dataset, summary, snapshot commit. Fetch, pagination, required-field, schema/count anomaly, Dataset, or summary failures prevent snapshot advancement. Storage and compute are linear in the complete England dataset.

This Actor covers England only. It reflects published register data, which varies by authority and can be delayed, incomplete, re-keyed, or corrected. Some official records omit a reference or organisation identifier; the official entity ID is then retained as the displayed reference and the authority is labelled `Not supplied`. Site presence is not a guarantee of availability, investment suitability, planning approval, housing delivery, or development opportunity. Postcodes are extracted from official site-address text when present; some records have none.

# Actor input Schema

## `mode` (type: `string`):

Use live official England data or self-contained sample changes.

## `signalTypes` (type: `array`):

Optional exact signal type filter.

## `localAuthorities` (type: `array`):

Optional exact official authority-name filter.

## `postcodePrefixes` (type: `array`):

Optional case-insensitive postcode prefix filter.

## `planningPermissionStatuses` (type: `array`):

Optional official permission status filter.

## `ownershipStatuses` (type: `array`):

Optional official ownership status filter.

## `minDwellingIncrease` (type: `number`):

Minimum absolute positive capacity delta to emit.

## `minDwellingDecrease` (type: `number`):

Minimum absolute negative capacity delta to emit.

## `baselineOnly` (type: `boolean`):

Store a validated full England snapshot without emitting signals.

## `maxItems` (type: `integer`):

Maximum Dataset items; the snapshot is never truncated.

## Actor input object example

```json
{
  "mode": "live",
  "baselineOnly": false,
  "maxItems": 100
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("starshaped_bullsnake/england-brownfield-development-opportunity-change-signals").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("starshaped_bullsnake/england-brownfield-development-opportunity-change-signals").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call starshaped_bullsnake/england-brownfield-development-opportunity-change-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starshaped_bullsnake/england-brownfield-development-opportunity-change-signals"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ApMPBW2bvJmkMfKj6/builds/1J0pCl1M1P9i9m7JH/openapi.json