This dataset contains the digital vectorial version of all plan elements — of the type of overprint indicative indication — of revised or removed outdated device requirements as described in VCRO Article 7.4.4/1, both the final approved and formatted ones. It also incorporates the suspensions and destructions of the Council of State. A plan element is an object by which the government concerned reflects the scope of (part of) the spatial option it has taken on the basis of certain urban planning regulations on the graphic plan, if it considers it necessary. This object is conceptually always traced back to a plane, line or point, to which a certain legend symbol has been assigned. In order to ensure the link between a “location” and the “full set of requirements applicable at that location”, it is necessary to unravel a plan in some complementary geodata layers in vector format. In this way, we obtain an unambiguous link between prescription texts and their corresponding plan elements. Pressure surface requirements concern a detail or an additional condition on a ground plane, irrespective of whether the latter is part of an earlier plan or plan. In practice, this means that for the areas concerned, the pressure requirements still have to be read together with one or more underlying requirements (of an older plan or the same plan), because they do not replace the underlying ground surface requirements. In a plan, urban planning regulations can be added that apply to an area, line or location that the plan creator does not want to geometrically determine. These are the so-called indicative indications. There are three types of indicative indications: points, lines and overprints.
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.