CASI and LIDAR Habitat Map

Open data API in a single place

Provided by Environment Agency

Get early access to CASI and LIDAR Habitat Map API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
vegetation, remote sensing, environmental monitoring, geoscientificInformation, LIDAR, CASI, imageryBaseMapsEarthCover, elevation, environment, Habitat Map
Quality scoring

Dataset description

This record is for Approval for Access product AfA439. A habitat map derived from airborne data, specifically CASI (Compact Airborne Spectrographic Imager) and LIDAR (Light Detection and Ranging) data. The habitat map is a polygon shapefile showing site relevant habitat classes. Geographical coverage is incomplete because of limits in data available. It includes those areas where the Environment Agency, Natural England and the Regional Coastal Monitoring Programme have carried out sufficient aerial and ground surveys in England. The habitat map is derived from CASI multispectral data, LIDAR elevation data and other GIS products. The classification uses ground data from sites collected near to the time of CASI capture. We use ground data to identify the characteristics of the different habitats in the CASI and LIDAR data. These characteristics are then used to classify the remaining areas into one of the different habitats. Habitat maps generated by Geomatics are often derived using multiple data sources (e.g. CASI, LIDAR and OS-base mapping data), which may or may not have been captured coincidentally. In instances where datasets are not coincidentally captured there may be some errors brought about by seasonal, developmental or anthropological change in the habitat. The collection of ground data used in the classification has some limitations. It has not been collected at the same time as CASI or LIDAR capture; it is normally within a couple of months of CASI capture. Some variations between the CASI data and situation on site at the time of ground data collection are possible. A good spatial coverage of ground data around the site is recommended, although not always practically achievable. For a class to be mapped on site there must have been samples collected for it on site. If the class is not seen on site or samples are not collected for a class, it cannot be mapped. No quantitative accuracy assessment has been carried out on the habitat map, although the classification was trained using ground data and the final habitat map has been critically evaluated using Aerial Photography captured simultaneously with the CASI data by the processors and independently by habitat specialists. Please note that this content contains Ordnance Survey data © Crown copyright and database right [2014] and you must ensure that a similar attribution statement is contained in any sub-licences of the Information that you grant, together with a requirement that any further sub-licences do the same. Attribution statement: © Environment Agency copyright and/or database right 2015. All rights reserved.
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