Update to tools v5. See https://github.com/openmaptiles/openmaptiles-tools/releases/tag/v5.0.0 for the list of all changes. Other OMT-repo specific changes: * removes `import-osm` docker usage, replacing it with `openmaptiles-tools` * quickstart builds faster because it uses postgres with preloaded water, natural earth, and lake centerlines tables. ### Makefile targets * `tools-dev` will open a shell in a docker to experiment and debug (instead of `import-sql-dev` and `import-osm-dev`) * separated `start-maputnik` from `start-postserve` * renamed `clean-docker` into `db-destroy` to make it more explicit * cleaner `db-start`, `db-stop`, `db-destroy` targets * `db-start-preloaded` is the same as `db-start`, except that it uses `postgis-preloaded` -- an image with preloaded water, natural-earth, and lake centerline data * `db-start` will not recreate the container if it already exists -- this way if it was started as preloaded, it will not be rebuilt. * better output messages ### Quickstart * uses `postgis-preloaded` image by default to make quickstart quicker. To start with a clean db, pass 2 parameters to quickstart, e.g. `./quickstart.sh albania empty`
43 lines
1.4 KiB
Markdown
43 lines
1.4 KiB
Markdown
# Keep the vector tiles updated
|
|
|
|
Once you have imported OpenMapTiles you can also keep it up to date by importing the latest OSM changes and
|
|
regenerating the tables.
|
|
|
|
## Import
|
|
|
|
You can either keep the database up to date based on the daily OSM change feed
|
|
or import specific change files.
|
|
|
|
### Keep Database Updated
|
|
|
|
You can use the new imposm3 feature to keep the database updated (thanks to the [work by @stirringhalo](https://github.com/openmaptiles/openmaptiles/pull/131)). This will automatically download
|
|
the OSM change feed and import it into the database.
|
|
After each run you should also have a list of tiles that have updated.
|
|
|
|
```
|
|
make update-osm
|
|
```
|
|
|
|
### Import Change File
|
|
|
|
Given you have a file `changes.osc.gz` in your import folder. Once you ran the import command you should also have a list of tiles that have updated.
|
|
|
|
```
|
|
make import-diff
|
|
```
|
|
|
|
## Generate Changed Tiles
|
|
|
|
After the import has finished **imposm3** will store lists of tiles in text format in subfolders of the `diffdir`,
|
|
named for the date(s) on which the import took place (`YYYYMMDD`).
|
|
Copy and merge the files to `tiles.txt` in the import folder (`data`), either manually or with the following command, which also removes duplicate tiles so they are only generated once:
|
|
```
|
|
cd data && sort ./*/*.tiles | uniq > tiles.txt
|
|
```
|
|
|
|
Now run the command to read the tilelist and write the vector tiles for it to a new MBTiles.
|
|
|
|
```
|
|
docker-compose run generate-changed-vectortiles
|
|
```
|