Snap Course

[Archdoog]

We currently pass the device's course through to the UI. On android this causes an issue where the map view drifts to north whenever you're stopped for more than second? or so. To avoid this, we should always provide the snapped (or snapped within range) course. We could also offer configuration since the ideal behavior may differ between platform. E.g.:

enum SnapCourseTo {
    /// Course provide by core is always the direction of travel from the route. As long as the user is "snapped", if they go
    /// off course, we should unsnap entirely and then the user puck should just show the device's location + course.
    case snapped

    /// This is the device's course within an allowable range off. Basically we report the actual device course up to the +- the amplitude.
    case deviceWithinRangeOfSnapped(amplitude)

    /// As it is now, we just report what the device tells us for course. Allowing the UI to drift to north.
    case device
}

[Archdoog]

This is done as of 0.11.0 👍