SkyDemon Forums

Relative Altitude of Traffic Targets

By Bealeyman - 1/5/2020 7:53:58 PM

I have suggested elsewhere (but cannot think where (is there a method to see all my posts ?)) that the relative height info is at times very difficult to see because of clutter. Of course here on the photo the 'traffic' is easy to see as regards height using the RADAR inset but if it had been bearingless traffic and one could only look at the main display the amount of in-cockpit time would be significant. I think this needs more consideration.

The route was EGKA EGKA via the Needles if you are puzzling and the Fantail for the return to Shoreham for the 07 rwy is already being depicted about 30 mins too early !! 
By Bealeyman - 1/5/2020 8:02:50 PM

I found my previous post it is on Bearingless Targets on the Traffic Screen. TD was interested at the time sorry my feedback was delayed.
By TimT - 6/23/2019 1:49:43 PM

The relative altitude of traffic targets displayed on the map and/or in Traffic Radar is arguably the most important information about a threat.

The relative altitude is currently included in the label belonging to the target (both with ADS-B target symbols, and with TPX-C related alert rings). For example "+0.8", or "-0.3", standing for 800 FT above, or 300 FT below respectively. The text size is:

- Controlled in the "Mapping" settings
- Linked together with the text size for all other waypoints, airport names, etc.
- And is limited to 140% of default text size

When a new traffic threat appears, I find it difficult to very quickly read the relative altitude:

- Even at 140% the writing is still small (after all the tablet 'vibrates' on a RAM Mount arms, and light conditions may be less than ideal)
- The most important + or - sign is really difficult to tell apart (after all, the difference between + and - is only a few vertical pixels on the screen, but it may be the difference between life and death up in the sky).

Therefore my suggestions are (not withstanding an entirely different, better way of doing it that the clever people at SD are capable of coming up with):

- Separate the settings for Traffic Label text size from the general text size settings
- Allow a wider wider range to set the text size (e.g, up to + 300%)
- Find a better way of differentiating between "above" and below" targets (I have no suggestion here how to do it - you'd need to play around with it)