Importing area data (OpenStreetMap, ALKIS)

Download buildings, streets and parcels from OpenStreetMap and official German survey data (ALKIS/ATKIS) and use them as a planning basis

VICUS Districts Page 1 of 9 in this chapter

Overview

VICUS Districts downloads area data for a planning area directly from the internet and displays it as a planning basis. Two sources are available in one common dialog:

  • Official survey data (ALKIS/ATKIS) of the German federal states: building outlines, street, path and square areas with street names and, optionally, cadastral parcels. They serve as a true-to-scale background drawing for route planning.
  • OpenStreetMap (OSM) worldwide: buildings (optionally as 3D solids), streets and terrain. The OSM buildings are also the data basis for automatically generating consumers.

Both sources can be combined in a single run.

Opening

  • Menu Import › Area data (OpenStreetMap, ALKIS) …
  • alternatively the Area button in the Import section of the Add geometry panel (right-hand side)

Download area data dialog

The Download area data dialog has two tabs: Download for retrieving data online and From file for OSM data saved earlier. Progress, the number of objects read and notes appear in the log area below the tabs.

Dialog for downloading area data with interactive world map
The import dialog with interactive world map: select the target area and download it or load it from a file

Selecting the area on the map

The Download tab shows an interactive map. When opened, it jumps to the project area if the project is already georeferenced, otherwise to the area last viewed.

InputEffect
Mouse wheelZoom
Drag with mouse button held downPan the map
Ctrl + dragDraw or redraw the selection rectangle
Drag inside the rectangle / on its handlesMove or resize the rectangle
Search location… field at the top of the mapSearch for a place and jump to it

If no rectangle is drawn, the visible map area is imported. The diagonal of the area may be at most 50 km; above 10 km VICUS Districts asks whether the download should be started anyway.

Data types

GroupOptionDefaultMeaning
ALKIS data (Germany)Buildings and streetsenabledBuilding outlines and street areas, with street names and centre lines wherever the region publishes them.
Cadastral parcels–Parcel boundaries of the real estate cadastre.
Open Street Maps (world wide)Building bodies, streets and terrain–OSM data of the area. Replaces an existing OSM dataset (after confirmation).
Extrude building bodies to 3DenabledBuilding footprints are extruded into 3D solids based on their estimated height; only active when OpenStreetMap is selected.

Downloading and importing

The import runs in two steps:

  1. Download retrieves the selected data for the area. The source attribution of the data is then shown below the map.
  2. Import to project adds the result to the project as one undo step. The main grid is hidden, since the map data now provides the spatial reference.

In a combined request, the survey data is loaded first, then the OSM data. If the OSM download fails, the survey data already loaded is kept and can still be imported.

From file tab

Read from file … reads an OpenStreetMap extract (*.osm) or a previously saved VICUS OSM file (*.vicosm) – useful for working without an internet connection or for sharing within the project team. The data replaces the OpenStreetMap data of the project. The Extrude building bodies to 3D option only applies to *.osm files; a *.vicosm file carries this setting itself.

Official survey data (ALKIS/ATKIS)

VICUS Districts determines the federal state from the selected area and queries its geodata services. The list of services is updated online when the dialog opens.

  • Outside Germany there is no official survey data. If the area cannot be assigned to a federal state, this part is skipped and OpenStreetMap is imported instead.
  • Not every state publishes all data types as open data. Missing data types are named before the download and skipped. In Bavaria, buildings and street areas are loaded tile by tile; parcels are not available there.
  • For very large areas (more than about 20,000 objects) VICUS Districts asks for confirmation, since that many objects can slow down the 3D view considerably.

Result: The survey data is created as the drawing GIS Data under Drawings/DXFs in the navigation tree, with one layer per object type (e.g. buildings, parcels, street, path and square areas, street names). The layers are drawn in grey levels with filled areas; street names appear as labels along the street areas. A repeated import adds to the same drawing without duplicating layers. The colour and visibility of individual layers can be adjusted in the object tree.

OpenStreetMap data

Among other things, the following is imported from OSM:

  • Buildings – footprints, optionally as extruded 3D solids including address information
  • Streets and railways – as polylines
  • Terrain – bodies of water, land use and other areas, if present in the area

For Europe, the data is retrieved from the OSM server of VICUS Software, outside Europe from the public Overpass server. If the server is busy, VICUS Districts automatically repeats the request several times with increasing waiting time.

The imported OSM data appears as a separate OpenStreetMap entry in the navigation tree. Individual categories (layers) can be shown and hidden there via the visibility icons. The area data is a purely referential display – it is neither simulated nor modified.

Turning OSM buildings into consumers

Network consumers can be generated directly from the imported OSM buildings – including automatically calculated connection power and heat demand:

  1. In the Add geometry panel, switch to the OSM to consumer mode.
  2. Select the desired buildings in the map view. Hold down the Ctrl key and drag a selection window to select several buildings at once. Individual buildings can be deselected again with a click.
  3. Several addresses within the same building can be merged automatically into a single consumer.
  4. Choose a building type and a building energy standard. From these, the specific heating power and specific heating demand are pre-filled; both values can be adjusted manually. Optionally, domestic hot water and cooling demand can be taken into account. The heated area is derived from the OSM footprint via the ratio of gross to net floor area.
  5. Specify whether the consumer is connected to a heat pump and, if applicable, enter the COP at design conditions – this affects the connection power on the network.
  6. Choose the target network (or create a new network).
  7. The summary page shows the gross and net floor area, connection power, heating power and heating demand for each building. After confirmation, the consumers are created as nodes in the network.
Selection of OSM buildings to generate consumers with a building energy standard
Generating consumers from OSM buildings with a selection window and a building energy standard

The generated consumers behave like manually created consumers: connection power and demand values can be edited afterwards in the Building demand tab.

Notes

  • OSM buildings only: The conversion into consumers works with the OpenStreetMap buildings. ALKIS buildings are a background drawing and cannot be converted directly.
  • Coordinates: If the project has no geographic reference yet, the first area data import sets it. This is used, among other things, for the elevation query of the network nodes and for the GIS export.
  • No terrain elevations: OpenStreetMap supplies no elevation information for the terrain. All nodes generated from OSM initially sit at z = 0, and the geodetic component in the pressure results is then zero. Run the elevation query after the import, once the network topology is in place.
  • Data quality: This limitation concerns the building data: building heights and addresses come from OpenStreetMap and may be incomplete. Check generated consumers on a sample basis, especially for small secondary buildings (garages, sheds) that should potentially be deselected.

Important in practice

OpenStreetMap is a good, fast basis – but not an official source. Building heights are often only estimated, and an automatically generated consumer is only as good as the OSM footprint. So check the pre-filled heated area and connection power before using them for sizing, and deliberately deselect garages, sheds and secondary buildings so that they do not end up as consumers in the network.

Stay up to date

New features, tutorials and updates delivered to your inbox.