20,741
edits
Using OSM Vector Data in FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Using OSM Vector Data in FlightGear (view source)
Revision as of 15:45, 31 January 2014
, 31 January 2014→Procedural Buildings & Cities (radi & vanosten): http://forum.flightgear.org/viewtopic.php?f=5&t=17598#p166681
m (→OSM2FG (Saitonen): http://forum.flightgear.org/viewtopic.php?f=5&t=17598&start=15#p177059) |
m (→Procedural Buildings & Cities (radi & vanosten): http://forum.flightgear.org/viewtopic.php?f=5&t=17598#p166681) |
||
| Line 196: | Line 196: | ||
'''vanosten:''' | '''vanosten:''' | ||
So the idea would be to procedurally generate buildings based on OSM data (not uploading to OSM!) based on other OSM data like streets, area classifications, ... I thought of enriching offline OSM data with buildings - which could then in a later step be used to actually generate buildings in Flightgear (or X-Plane with http://osm2xp.com/). Due to differences in landuse patters between e.g. cnetral Europe and USA the algorithm would naturally have to be configurable - however somewhere we need to start. | |||
Would that be a good idea? Has this already been attempted (I mean based on OSM data, not generic procedural cities)? | |||
I first let bob.pl generate all *.ac files and *stg entries. Then I parse the *.stg files for lines starting with OBJECT_STATIC, get out the lat and long, set the properties, wait 1 second and then get /position/ground-elev-m, which I write back to the file (instead of -9999). | I first let bob.pl generate all *.ac files and *stg entries. Then I parse the *.stg files for lines starting with OBJECT_STATIC, get out the lat and long, set the properties, wait 1 second and then get /position/ground-elev-m, which I write back to the file (instead of -9999). | ||