Modelling of a map of the conservation status of the FFH open-air habitat types of the Natura 2000 area Ennstal Alps/Gesäuse National Park Gesäuse

Open data API in a single place

Provided by Nationalparks Austria

Get early access to Modelling of a map of the conservation status of the FFH open-air habitat types of the Natura 2000 area Ennstal Alps/Gesäuse National Park Gesäuse API!

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

Dataset information

Country of origin
Updated
2022.08.02 00:00
Created
Available languages
English
Keywords
Biologie, Naturschutz, OpenDocument, Nationalparks Austria, Schutzgebiet
Quality scoring

Dataset description

This report documents the procedure for modelling a map of the conservation states of the Offenland FFH habitat types (FFH-LRT) in the Natura 2000 area of the Ennstal Alps/Gesäuse & Gesäuse National Park. The conservation status map available to date (digital only; Report: Zimmermann 2018) only shows the conservation status (ETZ) of forest FFA habitat types (including bushes), but also discusses the approach for all other habitat types. Our project is essentially the GIS technical implementation of the proposed modelling approaches. The demarcation of the FFH habitat types follows the FFH habitat type map (Zimmermann 2017a). As handled in Zimmermann 2018, we adhere to the indicators from Ellmauer 2005 and derive them from an existing data basis. For example, qualitative information on vegetation, such as the degree of shielding or the influence of pasture, can be obtained from the Habitalp aerial image interpretation. Other indicators, such as impairment, were derived from the path network and the climbing routes. Altitude data and calculated altitude levels and slope inclinations are generated from a terrain model (DGM) based on Airborne Laser Scanning (ALS). In contrast to the forest map version, the modelling of the conservation states is implemented in QGIS with the Graphical Modeller. For the calculation, various processing tools are lined up in a graphical model and at the end provide a layer with single-surface conservation states. The approach of using individual indicators to determine a conservation status for each individual area is maintained. The graphical models, with all calculation and combination logics, are comprehensible in digital and editable form. Already in the first version of the conservation status map, the Habitalp aerial image interpretation was identified as a significant source of error. In the present case, this concerns in particular the assessment of the vegetation structure, because the correct determination of the coverage proportions of trees, shrubs, herbaceous and dwarf shrubs is not always guaranteed or is not in the required sharpness; this is due to the fact that the openland polygons of the FFH habitat type map often come from terrestrial mapping, e.g. biotope mapping, and usually only represent parts of Habitalp polygons, the coverage percentages of which often do not correspond to those of the subsurfaces. Finally, according to the scheme indicated in Ellmauer 2005, an overall conservation status for the Natura 2000 site and the national park is shown separately by habitat type.
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