iFly GPS Forum

If AdventurePilot would deign to release the format for the .ifp files, then I'd bet some 3rd party enthusiast would be happy to create a program (for Windows, anyway; but if you sync files across other platforms to your Windows platform, then it would work for all) that would output the flight plan to kneeboard-acceptable formats.   :-)

(And, yes, I know this would imply that any significant changes made to the .ifp file format would require all 3rd party apps to re-write, but it's not an impossible task, just merely difficult (for both sides).  As it now stands, the .ifp file is pretty simple to deconstruct... most of the info is semi-colon delimited text... but it would be even better if it were officially detailed.)

I don't disagree that the log format is the biggest issue.  However, if one settled on the standard FAA VFR Form, it seems to me that would be a good start.  As for the ifp not having enough info....  there are, actually, enough resources available to devise a flight plan just based on the info in the .ifp, as long as only lat/long or airport codes are used....   for example, for distances I'd use great-circle calculations (based on lat/long); when only the airport code is given, a lookup of airport coordinates using the 3-letter code is possible (https://datahub.io/core/airport-codes) which would give me the lat/long and thus distance.  (I haven't yet found a resource for aviation fixes, VORs, intersections and their lat/long.... and, of course, custom waypoints would also have to be excluded).  Using a little geometry, the direction from one lat/long to another shouldn't be difficult.

I may do something like this just for myself, but I'd likely just output the data to a text file, then import that into Word for the final formatting/printing.

So, doable, with the limitations noted.  But before I embarked on something like this, it'd be nice to know the .ifp file format wasn't going to change (or, change very often).

Now, if AdventurePilot deemed to do this, then they likely can derive lat/long for fixes, VORs, intersections and custom waypoints, thus making it a better result.