12.12.2016, 22:52
Hi,
New to RouteConverter but it seams to be a pretty competent little software!
I have some requests related to flight planing, if possible.
1) I'm using an android app called FlyIsFun when out flying. Planing routes in that app is perfectly possible but a little bit tedious. When doing the planing however, I can add target altitudes between waypoints, similar as in Garmin .fpl.
I can also import/export from/to gpx/kml files, but then the target altitudes are not included.
Same for many other planing tools with possibility to export to gpx files, the altitudes are not included.
But FlyIsFun also have it's own internal file format (.gir) for import/export that includes altitude (and more). Would it be possible for you to contact Petr the developer, ask him for file specifications and implement conversion to/from his format?
My impression is that Petr is quite reasonable, have been in contact with him my self for requests.
2) Same as the first one, but for SkyDemon. It might be more troublesome to get the specifications
for their internal format (.flightplan), but worth trying. When exporting a SkyDemon route to .gpx the altitude is included in that file, but in a non-conventional way, might be a simple thing to change.
3) When adding positions between waypoint, RouteConverter automatically plans routes/tracks/waypoint lists as flowing ground tracks/roads. Would it be possible to only add new positions along the rumbline between two waypoints?
4) Again, when adding positions between waypoint, RouteConverter automatically plans routes/tracks/waypoint lists with the ground elevation for each position. Would it be possible to let the elevation for the new positions be the same as the preceding or acceding waypoint?
3) and 4) can be used if one likes to "test fly" a planed route in Google Earth for instance. If a .gpx file with only the original waypoints (with elevation/altitude included) are used with Google Earth, the entire leg between two waypoints will be ascending/descending lineary instead of keeping the same altitude until next waypoint. With my suggestion that behavior might be avoided.
I tried to attach some example files related to the mentioned software, but it was not possible?
Tried to change the extension to .txt but didn't work.
Thanks!
/Jens
New to RouteConverter but it seams to be a pretty competent little software!
I have some requests related to flight planing, if possible.
1) I'm using an android app called FlyIsFun when out flying. Planing routes in that app is perfectly possible but a little bit tedious. When doing the planing however, I can add target altitudes between waypoints, similar as in Garmin .fpl.
I can also import/export from/to gpx/kml files, but then the target altitudes are not included.
Same for many other planing tools with possibility to export to gpx files, the altitudes are not included.
But FlyIsFun also have it's own internal file format (.gir) for import/export that includes altitude (and more). Would it be possible for you to contact Petr the developer, ask him for file specifications and implement conversion to/from his format?
My impression is that Petr is quite reasonable, have been in contact with him my self for requests.
2) Same as the first one, but for SkyDemon. It might be more troublesome to get the specifications
for their internal format (.flightplan), but worth trying. When exporting a SkyDemon route to .gpx the altitude is included in that file, but in a non-conventional way, might be a simple thing to change.
3) When adding positions between waypoint, RouteConverter automatically plans routes/tracks/waypoint lists as flowing ground tracks/roads. Would it be possible to only add new positions along the rumbline between two waypoints?
4) Again, when adding positions between waypoint, RouteConverter automatically plans routes/tracks/waypoint lists with the ground elevation for each position. Would it be possible to let the elevation for the new positions be the same as the preceding or acceding waypoint?
3) and 4) can be used if one likes to "test fly" a planed route in Google Earth for instance. If a .gpx file with only the original waypoints (with elevation/altitude included) are used with Google Earth, the entire leg between two waypoints will be ascending/descending lineary instead of keeping the same altitude until next waypoint. With my suggestion that behavior might be avoided.
I tried to attach some example files related to the mentioned software, but it was not possible?
Tried to change the extension to .txt but didn't work.
Thanks!
/Jens
