2f60ca0730
Add a one-liner script to take the tile lists from the dated subfolders, merge and deduplicate them, and write it out to tiles.txt. Also update docs to reflect current behavior of `docker-compose run update-osm`.
43 lines
1.5 KiB
Markdown
43 lines
1.5 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.
|
|
|
|
```
|
|
docker-compose run 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.
|
|
|
|
```
|
|
docker-compose run import-osm-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
|
|
```
|