Source Gseng in the Johnsbachtal

Open data API in a single place

Provided by Nationalparks Austria

Get early access to Source Gseng in the Johnsbachtal API!

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

Dataset information

Country of origin
Updated
2013.10.14 00:00
Created
Available languages
English
Keywords
Naturschutz, Schutzgebiet, Binnengewässer, OpenDocument, Nationalparks Austria
Quality scoring

Dataset description

The debris source in the Gseng springs from an artificially piled pile of mixed-grained fine to block debris made of dolomite and lime, in which, among other things, asphalt chunks, granite cubes and various stone material from house demolitions etc. are stored. The original appearance of the source is unknown. It is likely to come from cracks in a lime bank, as it always originates in the same place despite the rearrangements in recent years. Presumably, however, the source mouth was always covered with rubble. At the time of the first take-up at the time of the first take-up in 2004, the source was in the raw state due to the constant excavations and pile-ups. Since the end of mining in autumn 2008, however, it has been able to regenerate.
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