Countryside Stewardship Woodland Sub Compartments

Open data API in a single place

Provided by Forestry Commission

Get early access to Countryside Stewardship Woodland Sub Compartments API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
planning, forestry, England, Felling, Woodland, land use, Grant Schemes, environment, New Planting, management
Quality scoring

Dataset description

Countryside Stewardship (CS) was launched in 2015 and is a Rural Development Programme for England (RDPE) grant scheme. It will contribute around £900 million over six years to help farmers and woodland managers look after the environment. Woodland is one of the scheme’s priorities and funding is available to: - create new woodland - support the preparation of management plans - address tree health issues - improve existing woodlands This dataset contains the sub-compartments that make up the CS applications approved by the Forestry Commission for the 2015 application window. The data was recorded within the same system as the predecessor to CS, the English Woodland Grant Scheme (EWGS). Therefore the structure of the data is very similar to that available for EWGS. Further information can be found online here: https://www.gov.uk/government/collections/countryside-stewardship-woodland-support There are two spatial datasets associated with the CS for the 2015 grant intake. These represent the Case Boundary and the Sub-compartments that are encapsulated by a case boundary. The spatial datasets are related within the CS database on a 'one to many' basis. This reflects the fact that a single CS case may have many sub-compartments. Likewise, a single CS sub-compartment may have several grant types applied to it. CS Sub-compartments Sub-compartments are the smallest mapped unit of grant aided area under the CS. Sub-compartments are aggregated up to Case Boundaries, and these boundaries are subsequently used to describe the overall extent of the CS case. A single case represents one application from an applicant for grant aid, and there may be a number of different grant types contained within a single case. All sub-compartments for cases that have been approved (and were not subsequently withdrawn without payment) for the 2015 CS intake are contained in this dataset. Attributes: WorkAreaID = CS sub-compartment unique identifier CaseRef = CS Case unique identifier AreaHa = Area in hectares of sub-compartment SubCpt = The sub-compartment reference for the case PropName = The case name FSArea = The Forestry Commission Area who dealt with the case CaseType = The case type WCG = Presence or absence of the CS grant type Woodland Creation (Y/N) WIG = Presence or absence of the CS grant type Woodland Improvement (Y/N) WPG = Presence or absence of a Woodland Management Plan (Y/N) FLA = Presence or absence of a Felling Licence Application (Y/N) DateApprv = The date the case was approved by the Forestry Commission CurrStat = The status of the case at the time the data was created Attribution statement: Contains OS data © Crown copyright [and database right] [year].
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