Limitation of the ÜG Elbe of 01.10.2018, amended 21.01.2019

Open data API in a single place

Provided by Stadt Dresden

Get early access to Limitation of the ÜG Elbe of 01.10.2018, amended 21.01.2019 API!

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

Dataset information

Country of origin
Updated
2026.04.03 00:00
Created
2019.01.11
Available languages
English
Keywords
hydrographie, lokal, gewässernetz
Quality scoring

Dataset description

Limitation of the ÜG Elbe of 01.10.2018, amended 21.01.2019 Floodplain of the Elbe in Dresden for a 100-year event (HQ100, 4370 m3/s): The previous set ÜG of the Elbe for a flood event, as it is statistically expected once in a hundred years (HQ100), applied since October 2004. Since then, it has been amended twice, first in January 2012 and later in June 2016 following the completion of the public flood protection systems in the districts of Innenstadt/Friedrichstadt and Pieschen/Mickten/Kaditz, each limited to the protected areas. The exclusion of the established ÜG of the Elbe has now been reviewed on the basis of updated model principles throughout the city and adapted to new findings. The state capital Dresden is obliged to do so in accordance with § 76(2) sentence 3 of the Water Resources Act (WHG). A two-dimensional hydrodynamic-numeric simulation model developed at the TU Dresden, Institute of Hydraulic Engineering and Technical Hydromechanics was used for the technical determination of the ÜG, which was comprehensively updated after the Elbe flood of June 2013 on the initiative of the Free State of Saxony at the Technical University of Nuremberg (2D-HN model Elbe). After a further model update, which was carried out in 2017 on behalf of the state capital Dresden again at the Technical University of Nuremberg, the modeled flood areas were determined for an HQ100, among other things. The new maps of the ÜG Elbe are again based on a flood event, as can be statistically expected once in a hundred years, flow rate 4370 m3/s at the Dresden-Augustusbrücke level. For this purpose, the flood areas calculated for HQ100 were homogenized and plausible. Calculated island locations < 500 m2 were integrated into the ÜG Elbe and calculated island locations larger than 500 m2 remained as island locations outside the specified ÜG. In the definition of the ÜG, as in the previous ÜG, the interactions of the Elbe with other flowing waters, groundwater and sewerage, which may also lead to flooding, as well as temporary constructions, e.g. sandbag walls or other protective measures taken to prevent flooding, were not taken into account. Excluded from the ÜG are the areas protected by public flood protection systems designed and constructed for an HQ100. This concerns protected areas in Dresden's city centre and Friedrichstadt, in the districts of Pieschen, Trachau, Trachenberge, Mickten and Kaditz as well as in the areas of Stetzsch, Gohlis and Cossebaude. The newly defined floodplain of the Elbe for an HQ100 was shown in maps in accordance with § 72(2)(2) SächsWG. With the public interpretation of the new cards in the period from 1 October 2018 to 15 October 2018 pursuant to Paragraph 72(3) of the SächsWG, the new ÜG became valid as a fixed ÜG Elbe. At the same time, the previous ÜG Elbe of October 2004 expired with its amendments. The amendment of 21 January 2019 concerns only one area in the area of the Enderstraße. A review of the defined floodplain showed that it is technically and legally justified not to designate an area west of the Ender Strait as floodplain calculated as flooded. Therefore, this area was removed from the ÜG and added to the flood-prone area. The ÜG ends there coming from the east at the Enderstraße.
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