You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Cargo integration requires data in a mix of SI/Metric and Imperial units. Because Helium is being used across the globe, and not only in the US, it would make more sense to use SI units.
The only field that is currently not in SI units is speed.
Changing the expected unit of the speed field would result in a lot of incorrect data being ingested. We therefore need a migration plan. I suggest something like this:
Add new optional fields speed_ms, speed_kph, speed_mph, speed_knots for metre per second, kilometres per hour, miles per hour and knots (as reported in NMEA) respectively.
Stop ingesting the speed field.
(optional) After a couple of months re-enable speed and interpret it as km/h.
The text was updated successfully, but these errors were encountered:
Currently the Cargo integration requires data in a mix of SI/Metric and Imperial units. Because Helium is being used across the globe, and not only in the US, it would make more sense to use SI units.
The only field that is currently not in SI units is speed.
Changing the expected unit of the speed field would result in a lot of incorrect data being ingested. We therefore need a migration plan. I suggest something like this:
speed_ms
,speed_kph
,speed_mph
,speed_knots
for metre per second, kilometres per hour, miles per hour and knots (as reported in NMEA) respectively.speed
field.speed
and interpret it as km/h.The text was updated successfully, but these errors were encountered: