From OpenStreetMap Wiki
Jump to navigation Jump to search

BAG import adressen en gebouwen

Voortgang van de BAG-import: aantal gebouwen met de aangegeven source tags in Nederland sinds november 2013.

Deze Wiki beschrijft de import van de BAG (Basisregistratie Adressen en Gebouwen) data. De BAG is beschikbaar onder een publieke licentie en bevat adressen en pandcontouren. Het is de bedoeling dat elke mapper die een import van de BAG uitvoert zich gaat houden aan de afspraken die door de Nederlandse community zijn gemaakt. Als je een gebied wilt importeren kun je contact opnemen via de volgende thread op het Nederlandse forum: importeren van de BAG

Voor de import van de BAG data gelden, evenals elke andere import, richtlijnen die deels verplicht zijn gesteld door de Data Working Group (DWG) van de OpenStreetMap Foundation (OSMF). De reden daarvoor is het gezond houden van de OSM database. Onderstaande tekst, van toepassing voor Nederlandse importers, is Engelstalig t.b.v. medegebruik door de DWG.

Translation of the above by (free version):

This Wiki describes the import of the BAG (Basisregistratie Adressen en Gebouwen) data. The BAG is available under a public licence and contains addresses and building contours. The intention is that every mapper who performs an import of the BAG will adhere to the agreements made by the Dutch community. If you want to import an area you can contact us via the following thread on the dutch forum: importing the BAG
For the import of the BAG data, as for any other import, guidelines apply that are partly made mandatory by the Data Working Group (DWG) of the OpenStreetMap Foundation (OSMF). The reason for this is to keep the OSM database healthy. The text below, applicable to Dutch importers, is in English for the benefit of co-use by the DWG.

Import guidelines for BAG

Import guideline Required BAG import
Step 1.1 - Prerequisites n/a The BAG data for the Netherlands contains building outlines, addresses, objects (Dutch: verblijfsobjecten; any buildingoutline has at least 1 object which for example shows the use for that object), houseboats (Dutch: ligplaatsen, only used in some municipalities), fixed caravan sites (Dutch: standplaatsen, used in some municipalities but at a low number). These will all be imported, eliminating several tags not required in the OSM datamodel.
Step 1.2 - Community Buy-in acceptance by the community This import has been discussed several times on the Dutch forum and the talk list. On Saturday 16 November 2013 a meeting has been held in Utrecht where 13 members of the Dutch community have taken decisions on the BAG import. Further community involvement will be enlarging the number of people importing to use as much as possible local knowledge and contacting local people who added addresses when an area is imported.
Step 1.3 - Documentation license, updating the catalogue and the import The BAG is provided by law[1] under a public domain license[2]. The import is listed in the Import/Catalogue. The import is described on this page.
Step 1.4 - Import Review n/a The import will be discussed on the import list starting 28 November 2013. A test import can be viewed here.
Step 1.5 - Uploading dedicated user accounts Dedicated user accounts will be used, made up of the normal OSM name of a community member followed by _BAG (<”myOSMaccount_BAG”>)
2. Make sure data license is OK yes see Step 1.3
3. Document your import on the wiki yes see step 1.3 and separate section below
4. Use a dedicated user account yes see step 1.5
5. Consider your tags n/a see separate section below
6. Keep server resources in mind n/a The import will be spread over several years, due to the fact that use of local knowledge is first choice.
7. Don't screw up the data! n/a The upload will be split into small parts capable for JOSM. Revert knowledge is available.
8. Don't put data on top of data n/a The current buildings will be replaced, copying all relevant data available (like names of buildings). The current addresses will either be replaced or these areas will not be imported, depending on the importer and the communication with the mapper of the addresses.
9. Consider simplifying n/a The BAG data is quite good, though a slight simplication will be used in order to prevent multiple nodes on a straight building way.

Import decisions for BAG

At a meeting of the Dutch community in Utrecht @ 16 november 2013 the following decisions have been made (including later comments by the talk-imports)

  • the reason for this import is to dramatically improve the quality of the Dutch address and building data. This data is available as open data. Already several mappers uploaded data from the BAG. It's better to structure this to keep the OSM database as consistent as possible.
  • the following data from the BAG will be imported: panden, adressen, fixed caravan sites (standplaatsen) and house boats (ligplaatsen). From the verblijfsobject database the function will be included in the building outline for reference purposes. For the panden the bagid and the start_date (bouwjaar) will be included. For addresses the street, housenumber, postcode and city will be included. Source will be BAG. Also a source data tag will be used.
  • addresses will be imported in an addressnode because in the BAG these nodes are within 5 metres from the entrance (in one building/one address cases) which is highly valuable information for actual use in OpenStreetMap. This is accepted from a Map Features point of view. The Dutch community is very well aware of the different points of view on this subject within the OSM community. After import the various methods which are accepted in the Map Features apply, which means that for example addresses can be manually put on a building outline in a one building/one address situation. In such an example the Dutch community prefers the entrance being set manually on that POI for routing purposes.
  • The associated street relation will not be used because it is too difficult for newbies.
  • All data to be imported will be preprocessed, which means that building outlines, address data, house boats (ligplaatsen) and static caravan sites (standplaatsen) will be made available for JOSM, using the correct tags, already validated on duplicate nodes and overlapping buildings. The preprocessing will be done by a JOSM plugin). The plugin will only be made available for mappers on request through a message on this thread at the OpenStreetMap forum: importeren van de BAG, which makes it easier to control the import including the compliance to the decisions.
  • Imports will be done in small parts only by using JOSM and using a separate import account <”myOSMaccount_BAG”>. Mappers of current address data will be contacted in advance for help on the import in that area. Current data will be preserved and only be replaced when the BAG data is better, which is almost always the case for building outlines. The mapper will decide on conflation.
  • OSM Inspector will be used after import to check for inconsistencies in addr:street and the streetname (for example Burg. ipv Burgemeester, v. ipv van, Stationsstraat ipv Stationstraat).

  • The full tagging for buildingoutlines is:
Key Value Comment
building apartments, house, commercial, industrial, retail, prison, yes -
ref:bag bagid as available in BAG Original bag id from field PAND_ID useful for future updates
start_date Startdate as available in BAG Year in which the building has been completed
source BAG -
source:date YYYY-MM-DD Date of the release of the imported BAG data
layer -1 Only for underground buildings

  • The full tagging for addressnodes is:
Key Value Comment
addr:street streetname as available in BAG -
addr:housenumber housenumber as available in BAG -
addr:postcode postcode as available in BAG (without space) -
addr:city city/village as available in BAG -
source BAG -
source:date YYYY-MM-DD Date of the release of the imported BAG data

  • The full tagging for ligplaatsen (outlines for houseboats) is:
Key Value Comment
building houseboat -
  • The full tagging for standplaatsen (outlines for fixed caravan sites) is:
Key Value Comment
building static_caravan -
  • Changeset will refer to source (as in latest JOSM version) and source:date. Comment text: "import {area}". Source text: "BAG YYYY-MM-DD"

Detailed instructions

Detailed instructions on the BAG Import via the OpenDataServices plugin on BAG import via ODS plugin

Related Pages