Flooding areas and danger zones Carinthia

Open data API in a single place

Provided by Land Kärnten

Get early access to Flooding areas and danger zones Carinthia API!

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

Dataset information

Catalog

Land Kärnten catalog

Country of origin

Austria

Updated

2026.04.03 22:00

Created

2022.10.10

Available languages

English

Keywords

HQ300, GDI, Überflutungsflächen, HQ30, Gefahrenzonen, HQ100, KAGIS

Datasource

Official portal for European data link

Quality scoring

Dataset description

Since June 2018, there has been an interface description of the ‘Digital Data Requirements for the Flood Specialist Database, Part II Hazard Zone Planning’ on the pages of https://www.bml.gv.at/. For a smooth data exchange, data templates are provided on https://github.com/msgis/swwat-templates for the spatial data formats OGC Geopackage (.gpkg) and ESRI Geodatabase (.gdb). The present OGD data package fills the following 4 data levels: * GZ100 (Medium probability zones - red, yellow zones) * GZ300 (low probability zones) * FUNCTION (functional ranges) * UFHQN (flooding areas - HQ30, HQ100, HQ300) The data templates used are based on the projection EPSG:31258

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