|
BernardBig
|
|
|
Group: Forum Members
Posts: 1,
Visits: 0
|
+x+xHello everybody, Althoug this is a rather old topic, it still has not been solved by SkyDemon or I could not find it ! When flying I like to be informed of flight level or altitude changes like I am for tracks
So far nothing is available in SkyDemon (again nothing I could find...) It would be nice to have a visual indicator on the map for TOD and BOC at minimum as Michael suggested
This combined with a visual and audible message with the indication of the target altitude would make life easier
Kind regards,
Bernard ----------------------------- Hello! When changing the cruise altitude at waypoints, Skydemon offers the possibility to select whether the altitude change should be executed before or after the waypoint; the virtual radar view is adapted accordingly. The pilot log, however, does not show this information. I would appreciate if the information whether an altitude change should be initiated either before or at a waypoint would be included into the pilot log. A simple possibility to do so would be to write TOC/BOC/TOD/BOD* behind waypoints where the altitude is changed. This would not introduce new waypoints and legs into the pilot log (there was already some discussion about adding TOC/BOD waypoints to the flight log automatically). Kind regards
Michael
* In addition to TOC/BOC/TOD/BOD, two additional notations would ne necessary for waypoints that are passed while climbing or descending. Such situations could arise when there is only a short distance between waypoints with altitude changes. - Maybe pictograms would be a better choice. Yes, it would be a big advantage to have BOC/TOC/TOD/BOD as visible automotive points on the route leg, corresponding with the radar view. I fact these new visible points cannot be compared with standard waypoints, because waypoints are geographically fixed. The discussed points must change position on leg automatically depending due to several flexible adapted parameters such as altitude level, climb/descent rate, TAS aso. Kind regards, Wolfy
|
|
|
|
|
ArnaudC
|
|
|
Group: Forum Members
Posts: 77,
Visits: 133
|
If this makes the cut, it should be an option. On longer routes, the PLOG is busy enough like it is IMO.
|
|
|
|
|
KimW
|
|
|
Group: Forum Members
Posts: 42,
Visits: 0
|
To me that would be a good option to mark TOC/TOD as waypoints or not. I think however it should be a toggle option, as I sometime have multiple small descents and climbs to avoid airspace, where this would just add clutter.
|
|
|
|
|
Andrew
|
|
|
Group: Forum Members
Posts: 28,
Visits: 87
|
I'd like to put my hand up for including the BOC/TOD/BOC/TOC in at least the PLOG. Primary reason is from a backup/safety perspective - I believe it's always important to have a printed PLOG + charts as a backup to an iPad with SD... and wouldn't want a device failure/battery incident to upend the flight. Certainly in South Africa, flight training and best practice includes a manual backup for any electronic devices - and these are the only items missing from the PLOG in my view.
Cheers Andrew
|
|
|
|
|
Wolfgang Stüger
|
|
|
Group: Forum Members
Posts: 3,
Visits: 0
|
+xWolfy, are you advocating showing these things on the PLOG, the main map, or both? Hi Tim, I would propose - on both. On PLOG - to have a complete list information and orientation concerning distances (time and way) for the preflight planning state. At this time, the points can be compared with fixed waypoints. And on main map - on the one hand, to have the visual map-orientation during planning - and on the other hand, especially during flight as intelligent automotive points .
|
|
|
|
|
Tim Dawson
|
|
|
Group: Forum Members
Posts: 8K,
Visits: 9K
|
Wolfy, are you advocating showing these things on the PLOG, the main map, or both?
|
|
|
|
|
Wolfgang Stüger
|
|
|
Group: Forum Members
Posts: 3,
Visits: 0
|
+xHello! When changing the cruise altitude at waypoints, Skydemon offers the possibility to select whether the altitude change should be executed before or after the waypoint; the virtual radar view is adapted accordingly. The pilot log, however, does not show this information. I would appreciate if the information whether an altitude change should be initiated either before or at a waypoint would be included into the pilot log. A simple possibility to do so would be to write TOC/BOC/TOD/BOD* behind waypoints where the altitude is changed. This would not introduce new waypoints and legs into the pilot log (there was already some discussion about adding TOC/BOD waypoints to the flight log automatically). Kind regards
Michael
* In addition to TOC/BOC/TOD/BOD, two additional notations would ne necessary for waypoints that are passed while climbing or descending. Such situations could arise when there is only a short distance between waypoints with altitude changes. - Maybe pictograms would be a better choice. Yes, it would be a big advantage to have BOC/TOC/TOD/BOD as visible automotive points on the route leg, corresponding with the radar view. I fact these new visible points cannot be compared with standard waypoints, because waypoints are geographically fixed. The discussed points must change position on leg automatically depending due to several flexible adapted parameters such as altitude level, climb/descent rate, TAS aso. Kind regards, Wolfy
|
|
|
|
|
Tim Dawson
|
|
|
Group: Forum Members
Posts: 8K,
Visits: 9K
|
I appreciate your desire to have that information on the pilot log, but I think it would add clutter that most people are not interested in. If many people would appreciate this addition we will of course consider doing the work though. In the meantime, since it is not our goal to put absolutely everything in the pilot log, it would be a good idea to check the Virtual Radar during flight. It's a tremendously powerful instrument and can be very helpful with vertical navigation.
|
|
|
|
|
grahamb
|
|
|
Group: Forum Members
Posts: 565,
Visits: 27K
|
+x+x+x- Maybe pictograms would be a better choice. Maybe a glance at the Virtual Radar from time to time would be all it takes? Yes, that would be a makeshift. But in my opinion, the pilot log should contain as much information as possible (as long as it doesn't get confusing, of course). With your argumentation, the altitudes, frequencies etc. etc. could also be omitted from the pilot log because they can be found somewhere else. If I print only a few pages on paper, it is the pilot log and not the virtual radar. I'll admit I had assumed you'd be using SD in 'Go Flying' mode on a tablet or phone.
|
|
|
|
|
miaelch
|
|
|
Group: Forum Members
Posts: 15,
Visits: 2
|
+x+x- Maybe pictograms would be a better choice. Maybe a glance at the Virtual Radar from time to time would be all it takes? Yes, that would be a makeshift. But in my opinion, the pilot log should contain as much information as possible (as long as it doesn't get confusing, of course). With your argumentation, the altitudes, frequencies etc. etc. could also be omitted from the pilot log because they can be found somewhere else. If I print only a few pages on paper, it is the pilot log and not the virtual radar.
|
|
|
|