The user should be able to record tracks, and view previous tracks.
- Start and stop recording from a control on the chart. Show elapsed time and distance while recording.
- Sampling that balances detail against size: a minimum interval, then a point when distance, heading change, or elapsed time crosses a threshold. Something near 2 s minimum, 10 m of travel, 5 degrees of heading, or 30 s elapsed is a proven starting point.
- Recording continues with the screen off and the app in the background, on iOS and Android.
- Discard a track that is too short to be worth keeping, rather than filling the list with dock noise.
- A track list sorted by name, distance, or proximity, with rename and delete.
- Draw the active track live, and past tracks when selected.
- Persist through a crash. Points are written as they are recorded, not at stop.
Background recording is a shell capability, not a plugin one, for the same reason device GPS is. The 600-point overlay track in the ownship plugin can stay as the live tail. This issue is about the recording that outlives the session.
Background position is the shell capability this depends on, and it is not covered by #32, which is about getting a fix at all. The track list needs a home in the chrome, which is #40.
The user should be able to record tracks, and view previous tracks.
Background recording is a shell capability, not a plugin one, for the same reason device GPS is. The 600-point overlay track in the ownship plugin can stay as the live tail. This issue is about the recording that outlives the session.
Background position is the shell capability this depends on, and it is not covered by #32, which is about getting a fix at all. The track list needs a home in the chrome, which is #40.