Sub-areas are used in the implementation of the Protected Area and Compensation Ordinance SchALVO where hydrogeologically defined sub-areas of a water protected area have different nitrate classes.
Water protected areas are classified according to the nitrate or plant protection product content in groundwater in “normal areas”, “nitrate problem areas” and “nitrate remediation areas”. In water protected areas with multiple water intakes, the lower water authority may establish sub-category areas if there are different raw water qualities within these sub-areas and the hydrogeological conditions allow for sub-area demarcation. A WSG shall consist of at least two sub-areas.
For the geometry data, the Official Property Register Information System (ALKIS) serves as the basis for recording.
Please note the following information on the completeness and quality of the data provided: due to inaccuracies in the acquisition of subject objects, non-valid geometries according to OGC schema validation occur occasionally. As GIS servers such as ArcGIS servers, GeoServers or UMN MapServer need to use/process more and more accurate data bases, the test routine is always further developed and encourages inaccuracies (e.g. by third-party software) in the tolerance range as well as in topological detection. This means that geometries can no longer be represented or captured. The contested geometry errors include, among other things, self-intersections (self-intersections) or double support points. The LUBW therefore cannot guarantee the completeness and stability of the Download Service (WFS). Therefore, if necessary, please check the completeness based on the presentation services (WMS) also offered.
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.