While the reduction of the threshold in delta (lat./long.) to trigger republication of status.json when in the SRV is very much welcomed (thanks!), the doubly variable nature of this threshold, in terms of disparity in absolute positional change at any latitude other than 0° and in terms of variation in magnitude of positional change depending on body diameter, is still a bit frustrating.
We know that the game can calculate absolute distance, i.e. distance to selected target, whether or not latitude / longitude / heading / altitude are displayed.
This being the case, it would be preferable if the re-publication of status.json could be triggered by a defined positional change, say SRV = 50m (0.005° delta latitude on an Earth sized body = 55.6m) and for Ships / SLFs, 2km (0.02° delta latitude on an earth sized body = 2,224m).
This would mean that the required distance travelled to trigger re-publication of status.json would be constant (for each vehicle type), regardless of:
1) the size of the body in question, i.e. 1 Arc° of travel on an Earth sized body is 111.2km whereas it is 538.6km on the water giant Outotch DB-O d6-1 AB 4;
2) heading, i.e. the Ship can currently travel, from the equator, at 45°, 135°, 225° or 315° for about 0.028 Arc° before triggering re-publication (0.0007 Arc° for the SRV);
3) the current latitude on that body, i.e. travelling parallel to the equator at higher latitudes currently results in reduced required distance travelled to trigger re-publication; 75% of that at the equator at ±41.41° latitude; 50% of that at the equator at ±60° latitude; 25% of that at the equator at ±75.52° latitude; etc..
Even on Outotch DB-O d6-1 AB 4, the minimum discernible change in position, i.e. 0.000001° of latitude, is 53.9cm so a 50m SRV position change would be at around 0.000093° and a 2km ship position change would be around 0.003714° - both well below the current 0.0005° / 0.02°.
I'd appreciate it if the measurement unit relating to triggering republication of status.json could be reconsidered - due to the inconsistencies raised above regarding the use of dimensionless degrees in setting the threshold for republication of position.
Regarding possible additions to status.json, when the vehicle has position, the radius of the body to which the position relates would be a very nice addition to the positional information already supplied.