Skip to content

Gustry/docker-osm

 
 

Repository files navigation

Docker-OSM

A docker compose project to setup an OSM PostGIS database with automatic updates from OSM periodically. The only file you need is a PBF file and run the docker compose project.

Usage

PBF File

In this example we will set up an OSM database for South Africa that will pull for updates every 2 minutes.

First get a PBF file from your area and put this file in the 'settings' folder. You can download some PBF files on these URLS for instance :

cd settings
wget -c -O country.pbf http://download.openstreetmap.fr/extracts/africa/south_africa.osm.pbf

You must put only one PBF file in the settings folder. Only the last one will be read.

OSM Features

In settings, you can edit the mapping.yml to customize the PostGIS schema. You can find the documentation about the mapping configuration on the imposm website: https://imposm.org/docs/imposm3/latest/mapping.html The default file in Docker-OSM is coming from https://raw.githubusercontent.com/omniscale/imposm3/master/example-mapping.yml

Updates

You can configure the time interval in the docker-compose file. By default, it's two minutes. If you set the TIME variable to 0, no diff files will be imported.

The default update stream is worldwide. So even if you imported a local PBF, if you don't set a clipping area, you will end with data from all over the world.

Clipping

You can put a shapefile in the clip folder. This shapefile will be used for clipping every features after the import. This file has to be named 'clip.shp'. When the database container is running, import the shapefile in the database using the command : 'make import_clip'.

You can remove the clip file : make remove_clip.

QGIS Styles

The database is provided with some default styles. These styles will be loaded automatically when loaded in QGIS. It's following the default OSM mapping from ImpOSM.

make import_styles
make remove_styles
make backup_styles

SQL Trigger

You can add PostGIS functions, triggers, materialized views in the SQL file.

Build and run

Now build the docker images needed to run the application:

docker-compose build
docker-compose up

In production you should daemonize the services when bringing them up:

docker-compose up -d

You can check the timestamp of your database by reading the file : 'settings/timestamp.txt' or you can use : 'make timestamp'

Display

In the makefile, you can switch to another docker compose project. The other one includes QGIS Server. When it's running, you should be able to open, on the host(not in docker), the index.html file and see OSM and QGIS Server showing PostGIS tables. The webpage is using Leaflet.

If you want to tweak the QGIS Project, you need to add a host in your in /etc/hosts:

127.0.0.1       db

Because in the docker-compose file, the link is made with the PostGIS database using the alias db.

In the background

architecture

Docker OSM Update

This docker image when run will fetch on a regular interval any new diff file for all the changes that have happened in the world over the update interval.

You can also specify a custom url for fetching the diff if you wish to retrieve regional diffs rather than the global one.

You can specify a polygonal area for the diff so that it will only apply features from the diff that fall within that area. For example providing a polygon of the borders of Malawi will result in only Malawi features being extracted from the diff.

Note that the diff retrieved and options specified here are not related to the initial base map used - so for example if your initial base map is for Malawi and you specify a diff area in Botswana, updated features in Botswana will be applied to your base map which only includes features from Malawi. For this reason, take care to ensure that your diff area coincides with the region covered by your original base map.

Once the diff has been downloaded, it is placed into /home/import_queue where it will be picked up by the long running imposm3 container, which will apply the diff to the database.

You should have 3 folders : osm_pbf, import_queue, import_done

Put a state file in base-pbf like this one : http://download.openstreetmap.fr/extracts/africa/south_africa.state.txt

docker build -t osmupdate . docker run -v $('pwd')import-queue/:/home/import-queue -v $('pwd')base-pbf/:/home/base-pbf -v $('pwd')import-done/:/home/import-done -d osmupdate

With -e, you can add some settings :

  • MAX_DAYS = 100, the maximum time range to assemble a cumulated changefile.
  • DIFF = sporadic, osmupdate uses a combination of minutely, hourly and daily changefiles. This value can be minute, hour, day or sporadic.
  • MAX_MERGE = 7, argument to determine the maximum number of parallely processed changefiles.
  • COMPRESSION_LEVEL = 1, define level for gzip compression. values between 1 (low compression but fast) and 9 (high compression but slow)
  • BASE_URL = http://planet.openstreetmap.org/replication/, change the URL to use a custom URL to fetch regional file updates.
  • IMPORT_QUEUE = import_queue
  • IMPORT_DONE = import_done
  • OSM_PBF = osm_pbf
  • TIME = 120, seconds between two executions of the script

If you are using docker-compose, you can use these settings within the docker-compose.yml file.

Docker ImpOSM3

This image will take care of doing the initial load for the selected region (e.g. planet, or a country such as Malawi) into your database. It will then apply, at a regular interval (default is 2 minutes), any diff that arrives in the /home/import_queue folder to the postgis OSM database. The diffs are fetched by a separate container (see osm_update container).

The container will look for an OSM file (.pbf) and its state file (.state.txt) in BASE_PBF.

With -e, you can add some settings :

You can adjust these preferences in the docker-compose.yml file provided in this repository.

Credits

This application was designed and implemented by:

With some important design ideas provided by Ariel Nunez (ingenieroariel@gmail.com).

Parts of this project are built on the existing work of others.

July 2015

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • C 72.6%
  • PLSQL 23.0%
  • Python 3.4%
  • Other 1.0%