Using OSM Vector Data in FlightGear: Difference between revisions

Using OSM Vector Data in FlightGear (view source)

601 bytes added , 30 January 2014

20,741

edits

@@ Line 11: / Line 11: @@
 Also see [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38354.html Canvas & Tiled Maps ] Note that osgEarth will probably soon be linked into FG by default according to [http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAP3ntysiT0x-Fd_xN%2BS4qqSV%2BDwh7FNk%2BMj7BeHhmz-FB%2B5y9w%40mail.gmail.com/#msg31901878], which means that GDAL/OGR can be relied upon, i.e. supporting GeoTIFF processing would be another useful option for any mapping/charting needs implemented via Tom's Canvas system.
+=== Procedural Buildings & Cities (radi) ===
+Radi has focused on OSM buildings/bridges in the past, but is now interested in procedural city generation in general. OSM xml data for LOWI region alone is 50 MB. Might be a bit heavy a download for some users. Radi discussed this with James at FSweekend last year: we could pre-process OSM data, extract what's useful for us, and ship the outcome with our scenery. OSM buildings for LOWI would then add perhaps 1MB or so. OTOH, if this is generated at run-time (and then cached), users could decide themselves if/what OSM features they wish/can afford.
 ===Populate FG world with OSM data (F-JJTH) ===