You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.igc 4.8KB

  1. IGC Data Format Notes.
  2. ======================
  3. Refer to Appendix 1 of
  4. for the specification of the IGC data format.
  5. A sample list of software applications that use data in IGC format can be
  6. found at
  7. GPSBabel can be used to translate data in IGC format to and from various other
  8. formats.
  9. Routes in other formats are used to represent IGC task declarations.
  10. Tracks in other formats are used to represent IGC recorded flights.
  11. Converting to IGC format
  12. ========================
  13. IGC files generated by GPSBabel will NOT pass security validation tests since
  14. the data they contain cannot be proven to originate from an approved flight
  15. recorder. For most software applications that use IGC files this is not an
  16. issue but for competition scoring, record and badge claims the generated files
  17. will not be accepted as proof of a flight.
  18. A track stored in another format (GPX for example) representing a recorded
  19. flight can be converted into an IGC file:
  20. gpsbabel -i gpx -f mytrk.gpx -o igc -F myflight.igc
  21. If multiple track segments are provided in the input file, the one with the
  22. most points will be used.
  23. A route stored in another format representing a task declaration can be
  24. converted into an IGC file:
  25. gpsbabel -i gpx -f myrte.gpx -o igc -F mytask.igc
  26. A route and a track in other formats can be included into a single IGC file:
  27. gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -o igc -F myflight.igc
  28. A similar result can be obtained by downloading the track log and routes
  29. directly from a GPS device connected to a PC. For example to create an IGC
  30. file from data recorded in a Garmin GPS connected to the first serial port of
  31. a PC running Linux:
  32. gpsbabel -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc
  33. For Windows operating systems:
  34. gpsbabel -t -r -i garmin -f com1 -o igc -F myflight.igc
  35. A waypoint file in another format containing a waypoint whose short name is
  36. "PILOT" can be merged into an IGC file. The description field of the waypoint
  37. will be used for the pilot name in the IGC file header:
  38. gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -f mywpt.gpx -o igc -F myflight.igc
  39. gpsbabel -w -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc
  40. Some formats such as GPX allow routes, tracks and waypoints to exist in the
  41. same file and can be used to fully populate an IGC file:
  42. gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc
  43. Converting from IGC format
  44. ==========================
  45. Data in an IGC file can be converted into other formats. For example to
  46. generate OziExplorer files containing tracks representing the recorded
  47. flight (myozi.plt) and routes representing declared tasks (myozi.rte):
  48. gpsbabel -i igc -f myflight.igc -o ozi -F myozi
  49. Or to GPX format:
  50. gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx
  51. Header information from the IGC file will be written to the description field
  52. of the track(s).
  53. If both pressure altitude and GNSS altitude are recorded in the IGC file, two
  54. tracks will be written to the new track file, representing the two altitude
  55. tracks. The latitude, longitude and timestamps in the tracks will be identical.
  56. Merging into IGC format
  57. =======================
  58. A route stored in another format can be merged with an existing IGC file that
  59. has no task declaration, to generate a new IGC file with a task declaration:
  60. gpsbabel -i igc -f myflight.igc -i gpx -f myrte.gpx -o igc -F mynew.igc
  61. A two dimensional (lat/lon) track recorded during a flight by a GPS receiver
  62. can be merged with a one dimensional (altitude) track recorded during the same
  63. flight by a barograph instrument. The result is a three dimensional IGC file
  64. representing the flight:
  65. gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc
  66. Sometimes there is a discrepancy between the internal clock in the barograph
  67. instrument and GPS time which can result in the altitude and ground positions
  68. not correlating correctly. This can be corrected manually by passing the time
  69. difference in seconds between the two time domains through the "timeadj"
  70. parameter. This can be any positive or negative integer:
  71. gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=27 -F my3D.igc
  72. GPSBabel can also attempt to deduce the time difference automatically. This
  73. is done by comparing the time that it thinks that you landed on the GPS track
  74. and the barograph and adjusting accordingly:
  75. gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc
  76. The same can be acheived by downloading directly from a barograph instrument
  77. supported by GPSBabel. For example with a Brauniger IQ Comp GPS variometer:
  78. gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc
  79. or:
  80. gpsbabel -i baroiq -f com1 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc
  81. Chris Jones
  82. Aug 2004