FlightGear Newsletter February 2018: Difference between revisions

Jump to navigation Jump to search
No edit summary
 
Line 43: Line 43:
=== Docker updates ===
=== Docker updates ===


Torsten was able to create a small chunk of scenery with my Docker image. For some reason, it turned out be be Hawaii ;-) After some facepalm moments and a couple of retries, here is the result: https://www.dropbox.com/s/qu5ysxbv7j1mkmy/PHNL-draft.jpg?dl=1 Created from SRTM-1 elevation data, NLCD landcover pulled straight from Martin's landcover database and airports layout from today's X-Plane gateway.  
Torsten was able to create a small chunk of scenery with his Docker image. For some reason, it turned out be be Hawaii ;-) After some facepalm moments and a couple of retries, here is the result: https://www.dropbox.com/s/qu5ysxbv7j1mkmy/PHNL-draft.jpg?dl=1 Created from SRTM-1 elevation data, NLCD landcover pulled straight from Martin's landcover database and airports layout from today's X-Plane gateway.  


Martin kindly granted direct read access to his database so Torsten can run ogr-decode with the Postgres datasource pulling in the raw data instead of using exported shapefiles (speeds up things a lot and saves many GB of disk space) It still needs some more tweaking (most notable, there are no OSM roads yet) and Torsten expects some suprises when processing large scale data. Anyway - this is a major step forward in becoming able to create regular scenery updates automatically. Definitely not for 2018.1 - but with a good chance later this year. This scenery has been created on a machine knowing _nothing_ about FlightGear, no simgear, no terragear, not even a C++ compiler. Just a plain Linux box with docker installed and our terragear image started as a container. A _huge_ THANK YOU to Martin for preparing this excellent data set and making it available! <ref>{{cite web
Martin kindly granted direct read access to his database so Torsten can run ogr-decode with the Postgres datasource pulling in the raw data instead of using exported shapefiles (speeds up things a lot and saves many GB of disk space) It still needs some more tweaking (most notable, there are no OSM roads yet) and Torsten expects some suprises when processing large scale data. Anyway - this is a major step forward in becoming able to create regular scenery updates automatically. Definitely not for 2018.1 - but with a good chance later this year. This scenery has been created on a machine knowing _nothing_ about FlightGear, no simgear, no terragear, not even a C++ compiler. Just a plain Linux box with docker installed and our terragear image started as a container. A _huge_ THANK YOU to Martin for preparing this excellent data set and making it available! <ref>{{cite web

Navigation menu