Osm2city.py Batch

Autogen Scenery

Started in	11/2013
Description	Improved autogen support for FlightGear using OSM data
Contributor(s)	radi, vanosten, Soitanen, portreekid
Status	Under active development as of 02/2016
Topic branches:
$FG_SRC	https://gitlab.com/osm2city/osm2city/
fgdata	https://gitlab.com/osm2city/osm2city-data/

Osm2city can now be used to create complete tiles. It simplifies the usage of the osm2city.py toolchain. Currently it is tested for windows, but is planned to be portable.

Features

• Building of tile directories. Done
• Generation of elevation map. Done
• Generation of download batch. Done
• Generation of osm2city batch. Done
• Generation of osm2pylons batch. Done
• Generation of roads batch. Done
• Generation of piers batch. Done

Workflow

Adapt params.ini

Since the next step distributes the params.ini to several subdirectories it is advisable to edit the template params.ini

build-tiles.py

Call build_tiles.py

python batch_processing/build_tiles.py -t w003n60 -f params_kp.ini -o params.ini

This step copies the params_kp.ini and adds the tilename as a PREFIX and outputs to params.ini.

#-- Scenery folder (typically a geographic name or the ICAO code of the airport
PREFIX = w010n50/w006n55

tools[ew]XXX[ns][YY].[sh|cmd]

Generated by build-tiles.py and contains the calls to all subdirectories of the tile [ew]XXX[ns][YY].

downloadXXXX.[sh|cmd]

Generated by build-tiles.py and contains wget calls to download all the subtiles of [ew]XXX[ns][YY] into the subdirectories.

osm2cityXXXX.[sh|cmd]

Generated by build-tiles.py and contains the calls to all subdirectories of the tile [ew]XXX[ns][YY].

Example