Access to Public Open Space and Nature by Ward

Open data API in a single place

Provided by Greenspace Information for Greater London

Get early access to Access to Public Open Space and Nature by Ward API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
greenspace, nature, parks, sinc, openspace, wards
Quality scoring

Dataset description

<p> <strong>Update October 2025: GiGL are no longer providing this dataset as Open Data. We are currently reviewing our approach to publishing open data, and this includes how the datasets have been used, and the associated impacts in relation to our mission, income and reputation. We will create new outputs based on the review findings by the end of 2025. Please&nbsp;</strong> <a href="https://www.gigl.org.uk/contact/" target="_blank"> <strong>get in touch</strong> </a>&nbsp;<strong>if you have any questions.</strong> </p> <p> <br /> </p> <p>Percentage and count of residential households within Wards, with access to at least one open space by specified type of space, and the amount/proportion of each ward that is open space with and without public access.</p> <p>Also the proportion of homes located within public open space, and access to nature boundaries.</p> <p>Areas of deficiency in access to nature are defined as built-up areas more than one kilometre actual walking distance from an accessible Metropolitan or Borough Site of Interest for Nature Conservation (SINC).</p> <p>The analysis of public open space is based on access to designated green/public open space and therefore <strong>excludes farmland</strong>, and other types of green space outside of the public open space category definitions within the London Plan.</p> <p>These measures take no account of additional public rights of way, that can also give the same benefits as more formal open spaces.</p> <p>Homes further away than the maximum recommended distance are considered to be deficient in access to that type of public open space (POS).</p> <p>In 2015 the recommended distances for each type, are:</p> <p>R - Regional Parks = 5km max</p> <p>M - Metropolitan Parks = 2.4km max</p> <p>D - District = 1.2km max</p> <p>LSP - Local, Small and Pocket parks = 400 metres max.</p> <p>For a definition of public open space types refer to the London Plan 2011, Table 7.2 <a href="http://www.london.gov.uk/priorities/planning/londonplan" target="_blank">http://www.london.gov.uk/priorities/planning/londonplan</a> </p> <p>Higher category parks also perform the function of lower category parks, e.g. a Metropolitan Park also functions as a District Park and a Local Park.</p> <p>The distance is actual walking distance (taking into account fences, railway lines, rivers etc.) to reach access points of parks and other, generally managed, sites, usually with some facilities.</p> <p>This measure takes no account of the quality or facilities at each open space.</p> <p>No account of local, small and pocket parks outside the Greater London boundary has been made, though all regional, metropolitan and district parks in the vicinity of London have been included.</p> <p>Residential addresses provided by Ordnance Survey.</p> <p>Wards in the City of London have been merged to create one area in 2013.</p> <p>2014 ward boundaries only affect three boroughs in which wards changed in 2014 - Hackney, Tower Hamlets, and Kensington and Chelsea. All other ward boundaries in London remain unchanged.</p> <p>Visit the Greenspace Information for Greater London (GiGL) website <a href="http://www.gigl.org.uk/" target="_blank">here</a>.</p> <p>This dataset is licenced under Open Government Licence (OGL v2).</p>
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.

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

Copyright © 2026. Made by Apitalks