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 20:28, 30 January 2014
, 30 January 2014→Procedural Airports (psadro_gm, zakalawe, papillon81): http://flightgear.org/forums/viewtopic.php?p=176132#p176132
m (→Background: http://forum.flightgear.org/viewtopic.php?f=6&t=21351&p=194425&hilit=procedurally+airports#p194425) |
m (→Procedural Airports (psadro_gm, zakalawe, papillon81): http://flightgear.org/forums/viewtopic.php?p=176132#p176132) |
||
| Line 66: | Line 66: | ||
=== Procedural Airports (psadro_gm, zakalawe, papillon81) === | === Procedural Airports (psadro_gm, zakalawe, papillon81) === | ||
we already have all the data to generate the ground polygons, inside FlightGear - that's exactly how the airfield chart / ground-radar work. And we can do it adaptively (more bezier interpolation on faster machines) and also get airports editable in mostly-realtime (unless the airport boundary changes). | |||
The trick is to make an OSG 'loader' which creates the airport geometry from the apt.dat definitions, which of course is exactly what genapts does - this is why I was working with Chris to make it fast enough to run inside the loader thread, in FG. | |||
I'd love to fully generate the apts at runtime. LEMD is probably the most complex layout, and genapt currently takes about 2.5 seconds to generate. I imagine it could be generated in 2 stages for LOD. 1 for runways and taxiways, which are really quick, the 2nd stage for the line data which is slower. | I'd love to fully generate the apts at runtime. LEMD is probably the most complex layout, and genapt currently takes about 2.5 seconds to generate. I imagine it could be generated in 2 stages for LOD. 1 for runways and taxiways, which are really quick, the 2nd stage for the line data which is slower. | ||
=== Procedural Buildings & Cities (radi & vanosten) === | === Procedural Buildings & Cities (radi & vanosten) === | ||
Also see [[Osm2city.py]] | Also see [[Osm2city.py]] | ||