Update steps for 'Using your own OSM data' (#889)

Add more clear step into quickstart.md for using own OSM data
fix #843
This commit is contained in:
Tomas Pohanka 2020-05-26 20:50:00 +02:00 committed by GitHub
parent 6feefb4145
commit b2ab969128
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -363,11 +363,11 @@ This is generating `.mbtiles` for your area : [ MIN_ZOOM: "0" - MAX_ZOOM: "7"
./quickstart.sh yukon # Yukon, Canada ./quickstart.sh yukon # Yukon, Canada
``` ```
### Using your own OSM data ### Using your own OSM data
Mbtiles can be generated from an arbitrary osm.pbf (e.g. for a region that is not covered by an existing extract) by making the `data/` directory and placing an osm.pbf inside/ Mbtiles can be generated from an arbitrary osm.pbf (e.g. for a region that is not covered by an existing extract) by making the `data/` directory and placing an *-latest.osm.pbf inside. Inside of folder have to be `docker-compose-config.yml` file too, otherwize whole folder `data/` will be deleted and `download-osm` will try to download osm.pbf file from `geofabric`, `osmfr` or `bbbike`.
``` ```
mkdir -p data mkdir -p data
mv my.osm.pbf data/ mv my-latest.osm.pbf data/
./quickstart.sh my ./quickstart.sh my
``` ```