In another thread of this forum, I complained that the new "Flight Track" feature in V2.2.0 of MFDVFR is not satisfactory, because important information is missing in the exported KML. For a demonstration, I performed a flight (EDFE-EDFE) with a comparison of two recordings (see image1.jpg):

The red line is the KML as exported from MFDVFR running on an ipad mini, and imported into Google Earth.

The blue dots have been exported from the app of an u-blox GPS mouse (recorded as plain NMEA text), converted by GPSBabel into KML, and imported into Google Earth. The app run on a notebook PC, the GPS mouse connected via USB.

Both, red and blue, have been recorded on the same flight. The coordinates as shown on the earth are more or less equal. The main difference is the time information, missing in the MFDVFR data, being contained in the u-blox data.

In image1.jpg, the lines and dots coming from the taxiway are before takeoff, the line and dots coming in from the left belong to the landing.

As the blue dots have GPS time information attached, you could prove with them your timely behaviour of the aircraft movement, of course within the GPS accuracy. As can be clearly seen in image1.jpg, the AC stopped - as is necessary - at the holding point of RWY 08, before takeoff. You CANNOT see this with the red lines. Thus, in case someone stated that you ignored the holding point, the red information (MFDVFR recordings) would be of no help at all.

You COULD prove with the MFDVFR recording, that you did not violate airspaces. However, as you cannot click on the red line in Google Earth (in MFDVFR you can't even show the track), you would almost certainly have to do some postprocessing of the "red" KML file, to provide evidence.

Completely different with the "blue" KML: In Google Earth you can click on every point (1sec apart) and get all the information you need. This is shown in image2.jpg, showing the reporting point "KILO" of EDFE. You have all you need at your fingertips. And in case you have to inspect the file, you just look for the point number - 990 in the image - and find it immediately.

Such or a similar picture - even if "only" 2D and perhaps "only" available offline - would be a great feature in MFDVFR. As it is now, it is just nice to look at, not more.

The GPS information is present, why not use it?



Views: 367


Reply to This

Replies to This Discussion

Hi Jeppesen Team!

The missing time information in the kml files is an issue for me as well! Without the time information a serious debriefing of a flight for example with cloudahoy is not possible. Please add the timing infos to the flight track function and the generated Kml files.

Many thanks!

Reply to Discussion




In this category you will find discussion which should support you in finding answers regarding general or technical questions.

124 discussions


Here we share useful information about new features and functions of Jeppesen Mobile FliteDeck VFR.

1 discussions

Blog Posts

iOS 12 Compatibility

Posted by Lars Wedegärtner on October 8, 2018 at 1:37am 0 Comments

iOS 12

Posted by Lars Wedegärtner on September 19, 2018 at 9:31am 1 Comment

iOS 12

Posted by Lars Wedegärtner on September 19, 2018 at 9:29am 0 Comments

© 2019   Jeppesen   Powered by

Badges  |     |  Terms of Service