Airport data (apt.dat) update

From FlightGear wiki
Jump to: navigation, search

FlightGear uses the same airport data as X-Plane, in the apt.dat format. This data has been updated a lot the last years. FlightGear however uses a deprecated data format (810 format) and needs to switch to the newer 850 format in order to enjoy all the updates.

Problems and questions

  • We cannot just update the scenery as FlightGear contains a "hard-wired" apt.dat in fgdata. Simply updating this file does not change the airport visuals, but internally, runway positions and frequencies will. This will result in a mismatch when using old scenery.
    • The xml files that can be put into every scenery folder (icao.threshold.xml and alike) are a small start to adress this issue, but they quickly come to a limit in cases where there are new runways/new airports or just a rename of a single runway, compared to the apt.dat file in fgdata.
  • In contrast to X-Plane we do not create our airports on-the fly on startup of FlightGear. So distributing a huge apt.dat 850 file with approx. 90% of the lines being bezier curves definitions might just be a waste of ressources. (We should also consider that the curves can be useful for drawing airport maps, eg. like the currently existing groundradar or other types of maps)
  • Apt 850 comes with an integrated signs definition for each airport, while FlightGear is currently shipping them via STG files.
  • Some airports were enhanced for FlightGear use but never committed to Robin Peel DB.
  • Some airports were created in FlightGear but just still don't exist in X-Plane.
  • Workflow has to be clarified: a user wanting to update its airport layouts should download the latest data at this place (to be defined), update the data (in WorldEditor), send it to this address. Changes will be updated in FlightGear scenery release every x months.

Proposals and solutions

  • Enhance the FlightGear scenery xml code to become independent from any apt.dat file, enhance the xml parameters to make a big apt.dat file in fgdata obsolete and thus distribute scenery data where it belongs: into the scenery folder.
  • There has been an attempt to expand the xml per airport into a data file with almost all available data from apt.dat. The taxiways have been kept out, but it covers all the rest of the data plus some additional data like threshold coords etc. This data is produced with recent X-Plane apt.dat and can be updated with every new X-Plane data cycle, goes along the current X-Plane data specs. Example: http://code.google.com/p/flightgear-world-scenery/source/browse/data/xplane-single/C/CA69.xml
  • Sign definitions from FlightGear can be written out to an apt.dat 850 format file (they are all tagged with the appropriate airport) to a 850 format text file (multiple, per airport?). Then should be submitted to Robin. TerraGear creates stg files with SIGN entries when creating the terrain.
  • The enhanced Flightgear 810 airports are currently subject to review by papillon81. Layouts that are still not available in the X-Plane apt.dat release will be submitted, double layouts (available in both FlightGear 810 and X-Plane 850) will be compared and a decision will be made.
  • Users reporting wrong/missing/obsolete/whatever airports should be pointed to the latest apt.dat X-Plane release. This is always the reference from now on. They can search the file for the ICAO code and use WED to load a layout and take a look at it (no need to build TerraGear for this). An aid for such cases would be a web frontend that builds apt.dat layouts submitted in text form and outputs them either as download (btg.gz) or for online viewing (WebGL).

Airports layout tobedone

Some of us have updated 8.10 layouts in FlightGear. We have to make sure their work is not lost. Either the 8.50 format layout is better, and then it will automatically be used. Either the 8.10 updated layout is better. Then, it has to be converted to the 8.50 format with WorldEditor and sent to Robin Peel database. Hereunder is a list of those airports which got updated. Please check whether the 8.50 data is better than the 8.10, and update the list below. Thanks.

FlightGear data
better than Robin's?
ICAO 8.10 8.50 Converted to 8.50 Sent to Robin Peel Official apt.dat was updated
01NK
0B7
11XS
1B1
1B5
1GB
1S0
4V8
5B2
5B9
6B0
6B6
79C
82C
B04
CSK3
CYHC
CYTZ
EBBL
EBUL
EBZR
ED03 Y Y Y Y
EDCJ Y N N N
EDDF Y N N N
EDDI Y Y Y Y
EDDK Y N N N
EDDL Y N N N
EDDP Y N N N
EDEN Y N N N
EDKB Y N N N
EDKL Y N N N
EDLE Y N N N
EDLN Y N N N
EDNF Y N N N
EDPU Y N N N
EDQH Y N N N
EDWJ Y N N N
EDWL Y N N N
EDWM Y N N N
EDXE Y N N N
EDXH Y Y Y Y
EDXI Y N N N
EETN
EFHK
EG32
EGBJ
EGEO
EGKA
EGLL
EGNF
EGPH
EGTG
EH01
EH02
EH05
EH07
EH08
EH09
EH10
EH13
EH14
EH15
EH18
EH19
EH20
EH21
EH22
EH23
EH24
EH29
EH30
EHAL N N Y Y
EHAM N N Y Y
EHBD Y N N
EHHA Y N N
EHLE Y Y Y N
EHMA Y N N
EHMM Y N N
EHOW Y N N
EHRD N N Y Y
EHST Y N N
EHTE N N Y Y
EHTX N N Y Y
EHVK N N Y Y
EHVL N N Y Y
EHYP N N N N
EKEL
ELLX
EP63 Y Y
EP65 Y Y
EP66 Y Y
EP67 Y Y
EP68 Y Y
EPBC Y Y
EPBY Y Y
EPDE Y Y
EPDK Y Y
EPGO Y
EPGY Y
EPGZ Y Y
EPIW Y
EPKA Y
EPKK Y
EPKR Y
EPKS Y
EPLR Y Y
EPLB Y Y
EPMM Y
EPMO Y
EPPC Y
EPPO Y
EPRA Y Y
EPRP Y Y
EPRZ Y
EPSA Y Y
EPSJ Y Y
EPSO Y Y
EPST Y Y
EPSW
EPWA
EPWR
EPZA Y Y
FJDG
FXME
KALB
KAQW
KBAD
KBDN
KBFL
KBGR
KBKE
KBLI
KBTV
KCWF
KDFW
KDLS
KDMA
KDRI
KDVT
KDXR
KEAT
KEDW
KFHR
KGFL
KHAF
KHBW
KHIE
KHIO
KHQM
KHRI
KIWA
KJFK
KLAX
KLEB
KLGD
KLKP
KLSV
KMAL
KMMK
KMPV
KNID
KNRA
KNUQ
KOLM
KOQU
KORD
KOSH
KOXB
KOXC
KPBG
KPDT
KPDX
KPLB
KPSC
KPSF
KRUT
KRYN
KSDL
KSEA
KSFZ
KSNC
KSPB
KTEX
KTPA
KTTD
KUAO
KUNV
KUUU
KVSF
KVUO
KWST
KYKM
LEPA
LFDV Y N
LFEB N Y N N N
LFED N Y N N N
LFEQ N Y N N N
LFJY
LFKX
LFLJ Y N
LFMV N N Y Y
LFNH N N Y Y
LFRH
LFRJ
LFRK
LFRL
LFRO
LFRT
LFRU
LHSY
LHZA
LILQ
LILV
LIME
LIMW
LKTB
LOKL
LOWI
LSMA
LZTT Y Y
MO06
NH05
NK60
NY64
NY65
NY66
NY89
PANC
PANK
PASI
PHDH
PHHN
PHJH
PHJR
PHLU
PHMU
PHUP
RJAW
RJGG
RJSA
SABE
SADF
SADJ
SADL
SADM
SADO
SADP
SADQ
SAHR
SAZV
SBAF
SBJR
TFFJ
TKPN
TNCM
TRPG
UEST
UKDD
UTTT
VAID
VT01
VT03
VT14
W23
XBEL
YSAR
YSSY