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.
This change will allow us to create airport dialogues sorted by country and (optionally) state/province/region. Initially, we can just set every one to 'U', or possibly apply some simple heuristics (every four-letter airport identifier starting with 'K' is in the U.S., every four-letter airport identifier starting with 'CY' is in Canada, etc.)
2. In $FG_ROOT/Airports/runways.dat.gz (the runway-level data file), add two new record types, 'W' for windsock and 'C' for control tower. The W record would look like this (where 'S' stands for 'sock' rather than the other thingy, and 'L' stands for 'lighted):
R KABC 29.650236 -96.579416 176.00 SL
The 'C' record would give the latitude, longitude, and view elevation of the control tower:
C KABC 29.651347 -96.580527 315.00
Yep, lovely. Those two look good to me.
- Julian
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel