Why do my Velocity Bands sometimes change slightly after editing them in the Cloud?

Velocity data, including Velocity Band settings is stored in units of meters per second (m/s) on the OpenField Cloud regardless of the User's settings or what values are being shown in the Band Settings. The Velocity values are specifically stored to 2 decimal places, in m/s.

This can cause the values displayed in km/hr or miles/hr to change slightly depending on the value entered, once applied to selected Athletes and converted back to km/hr or miles/hr.

For example, if 3.05 km/hr is entered as a band value it will be converted to metres per second (3.05/3.6 = 0.847), then rounded to 2 decimal places and stored by OpenField as 0.85 m/s.

When the Band setting value is then applied to an Athlete the already rounded 0.85 m/s value is converted back into km/hr to display as km/hr in the Band Settings screen. 

0.85 * 3.6 = 3.06

This causes the Athlete's band setting value to become 3.06 km/hr instead of the desired 3.05 km/hr