153
edits
Osm2city.py: Difference between revisions
Jump to navigation
Jump to search
m
added roof LOD cmd line, fixed OSM download URL example
(major update of workflow, adapted to new input file structure) |
m (added roof LOD cmd line, fixed OSM download URL example) |
||
| Line 45: | Line 45: | ||
FlightGear knows three standard LOD: bare, rough and detail. 'Bare' sets the drawing distance of the terrain, which may easily be 50 km or more. Drawing buildings 50 km out makes little sense (unless they are ''really'' tall), so we shouldn't use this level here. Of the remaining two standard levels, 'rough' is used for large and/or tall buildings, and 'detail' for smaller ones. | FlightGear knows three standard LOD: bare, rough and detail. 'Bare' sets the drawing distance of the terrain, which may easily be 50 km or more. Drawing buildings 50 km out makes little sense (unless they are ''really'' tall), so we shouldn't use this level here. Of the remaining two standard levels, 'rough' is used for large and/or tall buildings, and 'detail' for smaller ones. | ||
In the near future, osm2city will generate more complex roof shapes. This will increase the poly count further, and I believe it's a good idea to use another LOD 'roof' for complex roofs. Fortunately, we can change every aspect of FlightGear, and adding another LOD is easy. Use the FG command line | In the near future, osm2city will generate more complex roof shapes. This will increase the poly count further, and I believe it's a good idea to use another LOD 'roof' for complex roofs. Fortunately, we can change every aspect of FlightGear, and adding another LOD is easy. Use the FG command line | ||
--prop:double:/sim/rendering/static-lod/roof=2000 | |||
to set the distance for 'roof' to 2 km. If you want to adjust it via FG's GUI, copy static-lod.xml (from osm2city's git repo) to $FGDATA/gui/dialogs. | |||
== Planned Features == | == Planned Features == | ||
| Line 89: | Line 91: | ||
* create a project directory. We will use LOWI/ in this example. | * create a project directory. We will use LOWI/ in this example. | ||
* get corresponding OSM data in its native .xml format. | * get corresponding OSM data in its native .xml format. | ||
There are several options to get OSM data. | There are several options to get OSM data. You may find the [http://harrywood.co.uk/maps/uixapi/xapi.html XAPI Query Builder] helpful, it will generate a download URL that you can fetch with wget: | ||
wget www.overpass-api.de/api/xapi? | wget -O buildings.osm http://www.overpass-api.de/api/xapi?map?bbox=11.16898,47.20837,11.79108,47.38161 | ||
Put this data into LOWI/buildings.osm | Put this data into LOWI/buildings.osm | ||
* Now adjust the input file. Copy the template params.ini to LOWI/. Edit this file, adjusting (at least) the following (check comments in params.ini): | * Now adjust the input file. Copy the template params.ini to LOWI/. Edit this file, adjusting (at least) the following (check comments in params.ini): | ||
:* PREFIX = LOWI (the project directory) | :* PREFIX = LOWI (the project directory) | ||