36
edits
FlightGear Scenery Designer: Difference between revisions
Jump to navigation
Jump to search
→History and Philosophy: Added new section on what is needed to run fgsd, with some sources
(→Documentation: further refinement of this new section.) |
(→History and Philosophy: Added new section on what is needed to run fgsd, with some sources) |
||
| Line 36: | Line 36: | ||
Airports are loaded from the airport database file located in the FlightGear base package. It is not possible to edit an airport, but a new definition of an individual airport can be loaded from a file in X-Plane format. This kind of file are typically produced by the Taxidraw airport editor. | Airports are loaded from the airport database file located in the FlightGear base package. It is not possible to edit an airport, but a new definition of an individual airport can be loaded from a file in X-Plane format. This kind of file are typically produced by the Taxidraw airport editor. | ||
== What you need to run fgsd == | |||
PLEASE ADD TO THIS LIST OTHER PLACES WHERE THESE THINGS CAN BE FOUND. | |||
* fgsd itself. | |||
** Source code from [http://sourceforge.net/projects/fgsd/files/ SourceForge] | |||
** Windows binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here] | |||
* Elevation data from the SRTM ([http://www2.jpl.nasa.gov/srtm/ Shuttle Radio Topography Mission]), in .hgt file format, at either SRTM-3 or SRTM-1 resolution. Some possible sources are listed here. Please note that if you want your work to eventually be incorporated back into FlightGear, you have to be careful to use elevation data sets that are compatible with the GNU Public License. | |||
** [http://dds.cr.usgs.gov/srtm/ http://dds.cr.usgs.gov/srtm/] | |||
* Surface landuse data from the [http://mapserver.flightgear.org/ FlightGear Mapserver] | |||
* Aerial photographs that are keyed to latitude and longitude | |||
== Main window == | == Main window == | ||