VEHPI-20: Speed precision needs addressing



Issue Information

Issue Type: Bug
 
Priority: Major
Status: Closed

Reported By:
Ben Tasker
Assigned To:
Ben Tasker
Project: VehManPi (VEHPI)
Resolution: Done (2013-12-21 23:10:25)
Components: GPS ,

Created: 2013-12-21 15:13:11
Time Spent Working


Description
Because the speed is returned as a float, converting it to an INT sometimes leads to weird behaviour (0.01 being rounded to 1 for example)


Issue Links

Toggle State Changes

Activity


Not going to fix just yet as it'll make it easier to test state changes once the Journey recorder is implemented (won't have to spoof anything to make it look like we're moving)
Have cast fix.speed to an int before applying the conversion from m/s to mph to lower the likelihood of a precision error. Appears to be working. Commit b1f8978 refers
btasker changed status from 'Open' to 'Resolved'
btasker added 'Done' to resolution
btasker changed status from 'Resolved' to 'Closed'