Import/Poland Buildings

From OpenStreetMap Wiki
Jump to navigation Jump to search

This is an overview of the addition of building outline data for Poland. The data has been provided courtesy of GUGiK for use in OSM. For a list of other Esri-curated datasets that are available for mapping, please see Esri ArcGIS Datasets.


The goal of this effort is to allow contributors to use Poland Buildings Data to continue to expand to the coverage of buildings across the country, using this data from GUGiK which has near-total coverage of the country. This effort would facilitate the task of increasing coverage, while retaining the many buildings already represented in OSM.


Data preparation was performed in January 2023. This OSM-ready data was reviewed by the Polish OSM community for its suitability to be imported through editor tools such as RapiD. The edits to OSM are to be performed incrementally by OSM contributors, performing manual imports of the data in RapiD or JOSM.


The source building outlines were downloaded from GUGiK originally in December 2022 at the suggestion of the OSM Poland contributors, for the purpose of preparing for adding to OSM via editor tools such as RapiD. The GUGiK geoportal describes the original dataset in detail.

Freshness of data varies by region. Each year tens of counties are resurveyed and data updated.

The processed building outlines that could be added to OSM are available to access on ArcGIS Online (see Poland Buildings). You can Open in Map Viewer to preview (click features to view tags) or sign in to export data for offline use.

OSM ODbL Compliance: Yes, the data is provided with explicit permission for use in OpenStreetMap.

Data Preparation

The processed building outlines were created using these Esri Data Processing Steps for Buildings and Addresses.

The data has initially been prepared for community review with six tags on each feature: amenity, building, building:levels, historic, man_made, and tourism. Not all feature will have values for each of these tags.

Original data is in GML format. It was parsed using custom script and loaded into PostgreSQL+Postgis database. OSM data was loaded into the same database using imposm3.

Buildings that intersect with any OSM building were filtered out. Additional features were filtered out that either intersected abandoned or demolished buildings. Some features were manually flagged to be rejected from the import since they were demolished or no longer visible on aerial imagery.

Polish community created mapping between original values describing building types and OSM tags. It's available in GitHub repository:

Data Conflation

The processed building outlines data contains 375,281 buildings, most of which do not already existing as building features in OSM. Raw data that was provided to Esri to be included in RapiD can be downloaded from here: (We can turn on automatic process that will update the file weekly if that would helpful please create an issue in

Existing building features in OSM will not be replaced, because RapiD will only suggest the addition of buildings where there is no overlap with an existing building feature. OSM Poland contributors will be able to use tools such as RapiD to add new buildings using the processed buildings from GUGiK and to make adjustments to the building geometry and attributes based on local knowledge and the most current imagery. This process has a high degree of human oversight. This should improve detection of cases where a feature may be a false-positive, for example if it the building been demolished since the source imagery date, or if it was not a building to begin with (caravans, containers)

Data Updates

The plan is to perform the updates using a RapiD and an updated Map with AI plugin for JOSM (see Esri blog post on new tools in OSM editors for more detail). The new tools enable OSM mappers to access ArcGIS Datasets hosted in ArcGIS Online and select individual features to use while editing OSM. The mapper is able to select a feature, review and edit the feature geometry and available fields, and then save their edits.

The mapper has the benefit of using existing features that have been created by the data provider, along with their available field values that have been pre-processed by Esri, while also being able to compare that feature with existing OSM data (e.g. street names) and imagery to ensure it is accurate and consistent.