|T O P I C R E V I E W
||Posted - 20/04/2012 : 09:36:09
In the popup window for airspace warning I would appreciate to have a button to deactivate the shown airspace. I it really laborious to find that airspace in the list on the airspace page and following to deactivate it here after activating its info-window.
|9 L A T E S T R E P L I E S (Newest First)
||Posted - 23/04/2012 : 13:01:42
There is no such button available, to "disable for current flight".
You can do it in 2.4 page.
||Posted - 23/04/2012 : 12:55:12
What about deactivation for this one flight? Considering some club glider that is shared by several pilots during a day, however still using single LK hardware?
||Posted - 20/04/2012 : 19:06:55
Sure, I meant more than 2 hours. Anything up to 24 hours maybe. User choice.
||Posted - 20/04/2012 : 18:04:39
Why not for a complete day?
Best case would be a "this day" -button (please as direct access btn).
Many airspaces are not active at a certain day (weekend etc)
||Posted - 20/04/2012 : 14:38:54
I think too that maybe we can have more than 2hours asp deactivation...
Kalman is the asp master, right?
||Posted - 20/04/2012 : 11:48:06
Most AS are a stack of different blocks/pieces.
They are all handled as independent AS, we cannot do anything about it since it is coming from the airspace file which does not allow complex 3D AS structures. Disable an entire AS with all parts in nothing you want/should to do during flight.
||Posted - 20/04/2012 : 11:38:09
Yes and I already mentioned it:
I think it is important to have a graphical feedback of the airspace before you are going to disable it (forever!).
You should be aware which AS are inactive the day you fly and disable them on ground before you fly. If there really is a need to disable an AS in the air you must point out the AS and you get a graphical response in the sideview (and only there) about disabled airspaces. It is also to prevent unintended disabling.
Disabling an AS is like removing it. You must re-enable it manually. For temporary ATC permissions it is intended to acknowledge an AS.
||Posted - 20/04/2012 : 10:55:11
ok, thank you. I did not know.
Is there a reason for these additional two steps instead of having a disable button (it is a procedure to remember)?
||Posted - 20/04/2012 : 10:36:44
The workflow is intended different:
ACKnolage it (for 30 minutes)!
You can set up the ACK Time in setup page 2 airspaces to a longer time e.g. 2hrs
If you get a warning -> Analysis -> Touch the AS to be disabled -> Disable.
I think it is important to have a graphical feedback of the airspace before you are going to disable it (forever).
Maybe we should extend the ACK time setup to greater values (e.g. 12hrs = ACK for today).