Long-term vegetation monitoring data (1961-2013) from moorland burning plots established at Hard Hill, Moor House in 1954

Open data API in a single place

Provided by Environmental Information Data Centre

Get early access to Long-term vegetation monitoring data (1961-2013) from moorland burning plots established at Hard Hill, Moor House in 1954 API!

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

Dataset information

Catalog

Environmental Information Data Centre catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

Lecidea granulosa, Environmental Monitoring Facilities, North Pennines

Datasource

Official portal for European data link

Quality scoring

Dataset description

The dataset consists of long-term vegetation monitoring data from the Hard Hill burning plots sited in the Moor House - Upper Teesdale National Nature Reserve, Cumbria. An experiment to investigate the effects of rotational burning and grazing was initiated in 1954, consisting of a replicated block layout. Initial vegetation recording was carried out in 1961 and 1965 using a quadrat method and DOMIN scale. In 1972 onwards, vegetation was recorded using a pin frame. Data were recorded by staff from the Centre for Ecology & Hydrology and its predecessors. Full details about this dataset can be found at https://doi.org/10.5285/0b931b16-796e-4ce4-8c64-d112f09293f7

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