By order of 21 March 2019, the BVerwG dismissed the non-approval complaint against the judgment of the Berlin-Brandenburg OVG of 5 July 2018. As a result, the regional plan has been ineffective since 02.05.2019.
Regional planning (objectives and principles) of the Havelland-Fläming region on settlements (settlement areas, services of general interest, commercial development) and on free space (free space security, use of wind energy, near-surface raw materials).
Part B of the Havelland-Fläming Regional Plan 2020 was issued by the Regional Assembly of the Havelland-Fläming Regional Planning Association on 16 December 2014 as a statute (§ 2(4), first sentence, of the Act on Regional Planning and Brown Coal and Restoration Planning (RegBkPlG) in the version published on 8 February 2012 (GVBl. Article 9 of the Law of 11 February 2014 (GVBl. (I No 07) has been amended).
By decision of 18 June 2015, the statutes were approved by the Joint Land Planning Department Berlin-Brandenburg as the highest regional authority responsible for spatial planning, with the exception of the drawing provision ‘The exploitation of near-surface raw materials’ (Z 3.3.1) with the designation ‘VR 08’ (Section 2(4), second sentence and (3) of the RegBkPlG).
In accordance with point 3 of the approval notice of 18 June 2015, the decision exempt from authorisation is not set out in the definition card of this publication. The published articles of association correspond to the version of the Statute Decision of 16 December 2014, as approved on 18 June 2015. The publication in the Official Gazette No. 43 of the Land of Brandenburg and thus the attainment of res judicata took place on 30.10.2015.
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.