XPlanung dataset BPL “to change the development plans 09-02 ‘Hofherrnweiler-Süd 1963’ and 09-02/7 ‘Sauerbachstr./Schradenbergstraße’ of 1976 between Falkenstraße, Schradenbergstraße, Sauerbachstraße and Adlerstraße in Aalen-Hofherrnweiler”
Open data API in a single place
Provided by Bundesamt für Kartographie und Geodäsie
Get early access to XPlanung dataset BPL “to change the development plans 09-02 ‘Hofherrnweiler-Süd 1963’ and 09-02/7 ‘Sauerbachstr./Schradenbergstraße’ of 1976 between Falkenstraße, Schradenbergstraße, Sauerbachstraße and Adlerstraße in Aalen-Hofherrnweiler” API!
Bauleitpläne, XPlanGML, Bauplätze, Bauplatz, Bauleitplan, B-Plan, 09-02/13, Stadt Aalen, XPlanung, Bauvorschrift, Bebauungsplan, GDI-BW, zur Änderung der Bebauungspläne 09-02 'Hofherrnweiler-Süd 1963' u. 09-02/7 'Sauerbachstr./Schradenbergstraße' v. 1976 zwischen der Falkenstraße, Schradenbergstraße, Sauerbachstraße und Adlerstraße in Aalen-Hofherrnweiler, XPlanung 5.0, Bebauungspläne
The development plan (BPL) contains the legally binding determinations for the urban planning order. In principle, the development plan must be developed from the land use plan. The available data concerns the development plan “to amend the development plans 09-02 ‘Hofherrnweiler-Süd 1963’ and 09-02/7 ‘Sauerbachstr./Schradenbergstraße’ of 1976 between Falkenstraße, Schradenbergstraße, Sauerbachstraße and Adlerstraße in Aalen-Hofherrnweiler” of the city of Aalen from XPlanung 5.0. Description: amending the building plans 09-02 ‘Hofherrnweiler-Süd 1963’ and 09-02/7 ‘Sauerbachstr./Schradenbergstraße’ of 1976 between Falkenstraße, Schradenbergstraße, Sauerbachstraße and Adlerstraße in Aalen-Hofherrnweiler.
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.