World Heritage Site Engine Houses

Open data API in a single place

Provided by Cornwall Council

Get early access to World Heritage Site Engine Houses API!

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

Dataset information

Catalog

Cornwall Council catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

mineral_industry, Heritage, historical_site

Datasource

Official portal for European data link

Quality scoring

Dataset description

The World Heritage Site project utlitised historic and modern Ordnance Survey mapping with existing documentary research to define the number of Cornish type, and related, engine house sites across Cornwall and west Devon. The dataset includes extant engine houses, with an assessment of survival and condition where known, and those for which only a map or other documentary reference exists. For a definition of what comprises a Cornish engine house, see: Sharpe, Lewis, Massie, Johnson (1991) 'Engine House Assessment - Mineral Tramways Project', Truro: Cornwall Archaeological Unit (Cornwall County Council report) This dataset was created for research purposes and relates only to the date when it was created c.2001-2002. It should not be taken as an accurate and up to date representation of the survival of Cornish type, and related, engine houses on the ground.

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