Landscape protected areas are legally binding areas where special protection of nature and landscape is required 1. To maintain, develop or restore the performance and functioning of the natural balance or the regeneration capacity and sustainable usability of natural resources, including the protection of habitats and habitats of certain wild fauna and flora, 2. Because of the diversity, peculiarity and beauty or the special cultural-historical significance of the landscape, or 3. Because of their special importance for recreation. In a landscape protected area, all acts which alter the nature of the area or which are contrary to the special purpose of protection are prohibited, with particular regard to § 5(1) and subject to detailed provisions. Viewing object in the GDZ; MultiFeature class consists of a comprehensive feature class GDZ2010.A_nglschg and the business table with the material data (GDZ2010.nglschg). In addition to numerous in-house attributes, the following user-relevant attributes are present, these attributes are still preliminary and will change again in the foreseeable future: OBJECTID; SHAPE: Surface, line, point; OIDEXT: GISPADID; IDENTIFICATION: GISPAD identifier; Identifier ALT: Identification; NAME: Area name; GBAZ: Old identifier; PROJECT: Project origin;AMTSBLATT: The Official Journal; IN FORCE: In force; KRAFTS: In force since; EXPERIENCE: Outside of force; NUMBER OF FL: Number of areas; Project: Osiris Saarland; DOCUMENTS: Documents; ISPAPSCH: Inspire Application Schema; FLAECHE HA: Area in ha (official); GEOGENAU: Geometric accuracy; DMASSTB: Digitising scale; PROTECTION: Protection objective; EDAT: date of storage; LAW: Link to the Regulation;PROJECT: Project name;VSG:;FFH;
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.