Town, District and Local centre boundaries (UDP June 2006) - Rochdale Borough Council

Open data API in a single place

Provided by Rochdale Borough Council

Get early access to Town, District and Local centre boundaries (UDP June 2006) - Rochdale Borough Council API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Rochdale Borough Council catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

Datasource

Official portal for European data link

Quality scoring

Dataset description

Town, District and Local centre boundaries are a series of allocations relating to the Rochdale UDP June 2006. These allocations cover planning policies on shopping and the roles of centres including the extent of Primary and Secondary shopping areas within the main town centres (Chapter 10): G/S/1 – Hierarchy and role of centres (allocations of main the town centres) S/3 – Primary shopping centres (allocations of the primary shopping centre) S/4 – Secondary and central shopping areas (allocations of the secondary and central shopping areas) S/6 – District centre, local centres and linear commercial areas (allocations of local centres and Milnrow district centre)

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service