32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
|
# Building
|
||
|
In this repo, clone FGdata.
|
||
|
Save the [dsf2aptdat.py](https://github.com/mherweg/d-laser-fgtools/blob/master/dsf2aptdat.py) as well in this repository.
|
||
|
Then build the container with `docker build --tag aptupdate`
|
||
|
|
||
|
# Usage
|
||
|
You need a bunch of working directories under a <path> of your choice:
|
||
|
* logs
|
||
|
* output
|
||
|
* data
|
||
|
* tmp
|
||
|
* work
|
||
|
* stg
|
||
|
|
||
|
You need to put the elevation data into this.
|
||
|
This requires the .arr.gz files.
|
||
|
Those are expected to be put under work/SRTM-3/
|
||
|
And are supposed to have the structure of `<10x10 degree area name>/<1x1 degree area name>/<tile name>.arr.gz`
|
||
|
|
||
|
Start the container with
|
||
|
`docker run -it --name aptupdate -v <path>/logs/:/aptuptd/logs -v <path>/output/:/aptuptd/output -v <path>/data/:/aptuptd/data -v <path>/tmp/:/aptuptd/tmp -v <path>/work/:/aptuptd/work -v <path>/stg/:/aptuptd/stg --rm aptupdate bash`
|
||
|
|
||
|
In there all you should need to do is run `./aptupd.py`
|
||
|
|
||
|
You find the output in the respective directory.
|
||
|
under data, you'll find a file `airports-done.json` after the first run.
|
||
|
This keeps track of the built airports and their version to only run updates on airports which got changed on the xplane gateways
|
||
|
If you wanna rebuild an airport, open the file, look for the airport in question and change its id, then re-run the process again.
|
||
|
|
||
|
# Licenses
|
||
|
* The code in this repository is released under the Cooperative non-violent public license, see LICENSE.md
|