Skip to content

Subsystem user interface

rueckwaertsflieger edited this page Apr 25, 2016 · 1 revision

AMVR presentation layer

Parallel presentation

In a digitized world, separate gauges for all the information are obsolete. Instead, a highly parallel presentation is needed for not crowding the airfield manager's workplace. Whenever information objects own a position, the object should be presented with its location on a map.

Minimum interaction approach, if not zero

With a highly parallel presentation approach and many geo-located infos, presented as overly on a map, a presentation can do the job quickly. However, simple measures do not require a position on the map as is UTC. Therefor the main set of information presented in parallel should reflect the main situation of an airfield manager’s work, not forcing him to interact with the AMVR application itself.

Not inventing the wheel

As will become evident in the following, XCSoar provides most of the features needed in general to fulfill the job. There are just a few drivers or interfaces missing, which system integrators can implement themselves without restrictions of a product management. And, there are some more presentation tweaks missing. The only true gap is the possibility of an actual weather map overly, though every functionality needed is buried in the RASP data overlay display. So why not involve XCSoar? In most cases, the airfield manager is a pilot himself, so there is a chance, he might already know XCSoar and even more, be familiar with the presentation's user interface.

Another approach might be to further evolve ADS-B radar solutions just like Dump1090 or ModesDeco2, with the latter providing a sophisticated presentation layer as well, besides an excellent transponder receiver. As a glider pilot and XCSoar evangelist the author prefers XCSoar. There are so many functionality details XCSoar already provides, a different approach cannot compete.