Sandro,
Currently the re-publication of status.json would seem to be triggered by the change of any of the status flags or if lat/long change by over 0.02°, heading changes by 10° or more or altitude changes by over 5%, and is published, at most, every second. The magnitude of the positional information deltas that trigger re-publication seem at odds with the precision to which the information is provided in status.json, i.e. to the 6th decimal place for lat/long in degrees, to the nearest integer degree of heading and to the nearest metre of altitude.
When travelling at low speeds in a ship or even at high speed in an SRV this results in positional information becoming outdated, i.e. different from that displayed by the HUD, by more than the usual second between publications of status.json.
Positional information precision is, in my opinion, more important at low speed than it is at high speed yet the frequency of publication reduces at low speeds. On an Earth sized planet, at the equator, the player would have to move about could move 2.2km before triggering a re-publication of status.json. At latitude 60° this would reduce to 1.1km east/west and above latitude 75° it would be less than 576m east/west - all the while, the north/south re-publication threshold would remain at 2.2km. This results in a simple disparity between latitudinal and longitudinal resolution in terms of threshold to republication. If the republication threshold was the same as the lowest difference in the published information the difference in lat/long at the equator would equate to 11cm....
Can the magnitude of the minimum positional information deltas to republication be reconsidered? Maybe set to the same as the smallest discernible difference on the HUD?