The topic covers the Upper Earth River Basin Areas (EZG) for surface waters in Dresden, with at least one EZG defined for each flowing water, except for a few exceptions.
On the outskirts of the city, passability to the entire Saxon dataset was established. The EZG’e were calculated using GIS tools (SAGA GIS 2.2.0, Quantum GIS 2.8.1, Geospatial Modelling Environment GME 0.7.3), among others, based on the following data: — GeoSN digital terrain models (DGM) with grid widths 0.5 m and 2 m (fly 2009)
— Water network of the city of Dresden (with Elbe as polyline, as of 20.03.2015)
— Catchment area dataset of the LfULG (Saxony-wide)
— LfULG flow water dataset (ATKIS-based, Saxon-wide)
The following data is displayed for each EZG:
— GEWAESSER:
Name of the water to which the catchment area belongs.
— GEWAESSERSYSTEM: Overarching water system.This attribute is used, among other things, for the assignment to the corresponding water cover.
If Gewaesser is a main water or a water does not flow into a larger water, at least partly in Dresden, then GEWAESSERSYSTEM=Gewaesser is — WAESSERKENNZAHL:Water code (GEWKZ) according to LAWA method for gewaessers
— AREA CODE: Encryption of the EZG with area code (GEBKZ) according to LAWA method = unique numbering of the EZG, coordinated with the total Saxon dataset.
— START/END:Start and end of the EZG in relation to the waters to which the catchment area belongs.
Start=source and ENDE=Earth in... states that it is the total undivided EZG of the corresponding water.
— FLARE:
EZG area in m²
— AEND:
Date of the last change
— STATUS:
Status, A=current
— CATTIME:
unique internal numbering of the graphic object
— KATNAM/TYPE:
other internal names for the graphic object
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.