David Megginson wrote:
I'd like to propose the following changes to our current airport data formats:
1. In $FG_ROOT/Airports/basic.dat.gz (the airport-level data file), add two fields containing the ISO 3166 country code and a country-specific region code. Either can be represented by 'U' if unknown. For example, here is the current entry for KSFO:
A KSFO 37.618763 -122.374926 13 CYN San Francisco Intl
Here is a revised entry with the new fields:
A KSFO 37.618763 -122.374926 13 US CA CYN San Francisco Intl
It seems *awfully* redundant given that there is already the Id *and* the geographical location. I have difficulty imagining that a high enough proportion of these will be determined and maintained to make it worthwhile. I do see why you want it though, and agree it would be nice to be able to get a list of airports in "my" region, by name of region rather than by lat/lon.
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.
My 5 cents:).
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
