GNSS Flight recorders

General
FAQ (6 Oct 08)
Home (6 Oct 08)

Manufacturers
CIMA Approved (6 Oct 08)
GAC Approved (29 Jul 02)
IGC Approved (28 Jul 02)

Software
Specification for FR software (15 Jan 09)
Specification for FR software.doc (77k) (15 Jan 09)
MLR data transfer (6 Oct 08)
MLR firmware (6 Oct 08)
MLR Flight Recorder instructions.pdf (107k) (1 Aug 05)
MicroFLAP (27 Jul 05)

spare
2003 WMC reliability analysis (5 Sep 03)

Standard
About the standard (6 Oct 08)

Utilities
microFLAPload (5 Jun 09)
File conversions (6 Oct 08)

Utilities OLD
File Conversions (20 May 09)
Showfile (26 Oct 05)

Contact rmh

Utilities OLD: File Conversions
Updated 20 May 2009

Convert files between different formats
You can use this page to convert files between different formats. Simply select the source file, the format it is in and the format you want it converted to.
New feature: You can also view the data on a map, click 'View now!', see notes below.

Source file
Source format
Convert to
        
    Viewing notes
  • You need to enter a Source file and Source format, Convert to can be left blank. Press View now! and wait a bit....
  • Tracks are 'compressed' to a maximum of 300 points, routes to 100. (otherwise it will overload your browser).
  • Tracks are blue, routes are red.
  • A new track is started once consistent movement of more than 5Km/h is detected and stopped once consistent movement drops below 5 Km/h. All the 'nearly stationary' track points are discarded.
  • Markers with 'W' are waypoints, 'E' are events, with 'S' and 'F' are the start and finish of tracks or routes. Click on any of them to get more info.
  • Track lengths Etc. are only approximate and based on a simple spherical Earth model. Go to the distance calculator to make FAI approved distance calculations.
  • Warnings: Will only work on modern browsers: MSIE6, Firefox, Safari. If you decide to try viewing a file containing a lot (100+) of markers then it will probably kill your browser. This is pretty much a first attempt at integrating the amazing Google maps API, so it may not swallow all the data you try throwing at it.
    Converting notes
  • The conversion process discriminates between data types. This means that you will get no content in the resulting file if you attempt to convert between files of exclusively different data types, eg a waypoint file to a track file. However, where source files contain multiple data types (eg .IGC files), then only the appropriate data type is written to the destination file. This enables you, for example, to extract PEV's (pilot 'marks') as waypoints from an .IGC file.
  • For an unknown reason this converter chokes on really long source file names. Keep the name of your source file reasonably short!
  • As time goes by more conversion possibilities will be added. If you have a particular need of one missing here or have found a problem with an existing one, contact rmh
  • Routes are only displayed in some software correctly (eg OziExplorer) if you have loaded the appropriate waypoints first.
Compatibility
Although all formats contain lat & lon, some formats don't contain either altitude and/or time. If altitude is not supported in either format, it is set to zero. If time is not supported in either format it is set to the time the conversion was made.
FormatAltitudeTime
FAI International Gliding Commission (*.igc) YY(1)
FAI General Aviation Commission (*.gac) YY(1)
OziExplorer waypoints (*.wpt) YY
OziExplorer track file (*.plt) YY
CouTraCi & SkyForce logger track (*.dat) YY
SeeYou waypoints (*.cup) YN
CouTraCi, Cambridge, Pocket-Nav & GPS-NAV waypoints (*.dat)NN
OziExplorer route file (*.rte) NN
OziExplorer event file (*.evt) NN
Memory map waypoints; 'Maptech terrain mark file' (*.mxf) NN
Memory map route; 'Maptech terrain route file' (*.rxf) NN
Memory map track; 'Maptech terrain track file' (*.txf) NN
(1) = When reading: If date is not recorded in the header or 'C' record then convert date is used.