The ground stations will 'mostly' be of the OGN-R variety
in FLARM speak these are defined as a STATIC OBJECT
At the moment we have astrange situation whereby filters are applied in 2 places, this is not a great idea to be honest.
If we consider a hose pipe with PilotAware supplying data at the source, and the navigation device (sprinkler) is at the destination, should PilotAware choses what it sends to the navigation device, or should the navigation device choose what it does with the data ?
We have been undergoing a 'feature creep' exercise, whereby more of the filtering is being done at the PilotAware data supply, rather than at the other end of the receiver
A good example of this is the Horizontal/Vertical separation filter
This filter now exists in PilotAware (to serve SkyMap and some other systems without these filters), but EasyVFR and SkyDemon have similar filters for restricting display of targets within X ft horizontal
This is undesirable, because it becomes unclear as to where throughout the pipeline of data, the filters are applied.
So in the case of ground-stations, or static objects of any kind (we have had proposals for Glider Winch etc)
should we restrict the data supplied at the source (PilotAware), or filter the data at the destination (Nav device).
I am reluctant to add more switches wherever possible, one of the criticisms I hear from many non-tech users, is how confusing it is to configure appropriately.
Thx
Lee