On Tue, 14 Oct 2003, Matevz Jekovec wrote: > IMO, we should include all these data in seperated .xml file for each > airport. In airports.tgz there should only be an international code of > the airport, lat/longitude and a reffering xml file for that airport. > That xml file should include all the data about buildings surrounding > it, taxiways positions, parking spaces, windsocks, ATC stuff etc. > FG should read the airports.tgz file completely, but seperated xml files > on demand.
If you do that then when you try to display a list of airports in the local area then you need to: 1. Calculate which airports *are* in the local area (because they're not already classicied into continents/countries/whatever). 2. Read the xml file for each one, because we don't have the name in the airport directory. This would be SLOW. There needs to be just enough info in the airports file to be able to quickly provide an index. The the rest of the details can be read from a seperate file once an airport is selected. -- Jon Stockill [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
