HIGH_LATENCY2 has not GPS status

[David Harty]

The original (obsolete) HIGH_LATENCY message had two fields for GPS, gps_nsat and gps_fix_type. The new HIGH_LATENCY2 has no reporting of GPS status. This causes a constant red error display in the Mission Planner HUD. We have worked around this by re-adding gps_fix_type to a custom implementation of the mavlink HIGH_LATENCY2 message, however this requires us to build our own version of any GCS software (mavproxy, Mission Planner QGS ...). We would rather remain compliant with the standard but GPS fix type is important to us, especially over high latency links. Is there any chance that a gps fix type could be added back to HL2 message or re-incorporated into a HL3 message? Was it deemed un-useful in some past committee standards review meeting? Regards.

[Hamish Willee]

The information in HL/HL2 is high latency. GPS status sent in such a message is pretty pointless - if you were to display it you would have to show it in red anyway to indicate it can't be trusted/isn't current. 

Your best bet would be to suggest to mission planner upstream that when on an HL link the icon is grey to indicate that the data is expected to be out of date, rather than red indicating this is an unexpected case.