Record Path: Phase 3 - Advanced Features #8385

New issue

Open

opened 2024-06-04 20:47:30 +00:00 by oleg-rswll · 0 comments

oleg-rswll commented

2024-06-04 20:47:30 +00:00

Member

Requirements for phase 3 will be compiled here. Ideas and suggestions are welcome in the comments. Dev for this phase will start after phase 2 is completed.

Pleas read requirement for the previous phases to be familiar what will be included in those:
organicmaps/organicmaps#8215 Phase 1: Trace Path
organicmaps/organicmaps#8214 Phase 2: Record Path

Overview
The first phase of the feature, Trace Path, enables seeing on the map the path that was traveled. The second phase, Record Path, turns Trace Path into a recorder that can be used both to trace a path and record it.

This phase, is to add functionality which would be useful beyond a basic recorder, addressing the most common use cases for recording.

Problem Statements

Very little data is displayed about the recorded path, and no statistics are available. A significant amount of data is collected during the recording, but it is not displayed, and no stats are calculated from that data. Having more information about the recording would be very useful and motivating to see.
A recorded path cannot be edited after it has been recorded, to remove unnecessary parts of the recording which would not be useful, for example the part before a hiking trail starts, or after the hiking trail ends.
Stats for a trail recording could be inaccurate if there are stops being made, for example for lunch. This gives an inaccurate view about the trail time and other stats.

Use Cases
Stop Button

Stop for a longer time (e.g. lunch) and pause recording to save battery
don't record side trips to keep focus on the main route
Don't record particular sections / side trips for privacy reasons
Exclude loitering time from the stats

Ideas
The suggestions in the comments about potential functionality to implement in this phase. As the process proceeds, these will be defined in more detailed and scope for this item will be determined.

Activity recorder:
- Activity type selection
- Stats (time, distance, speed, max speed, elevation gain/loss, etc)
Pause button, to be able to pause a recording, for example for lunch, and then later continue.
Edit the start and end point of the recorded path. When tapping and selecting the track on the map its name, start and end points can be edited (dots/arrows that can be moved on the map?), and track information can be displayed.
Path showing different colors based on speed/pace which is user defined.
Save a track at any time without stopping recording, for example, by highlighting it on the map, like a lap tracker.

Design
https://www.figma.com/design/5R5LmdM6L4GyfWjSrtlFqZ/OM-Track-Recoding-by-KK?node-id=0-1&t=jki69EK76A23HP8S-1

Requirements for phase 3 will be compiled here. Ideas and suggestions are welcome in the comments. Dev for this phase will start after phase 2 is completed. Pleas read requirement for the previous phases to be familiar what will be included in those: https://git.omaps.dev/organicmaps/organicmaps/issues/8215 Phase 1: Trace Path https://git.omaps.dev/organicmaps/organicmaps/issues/8214 Phase 2: Record Path **Overview** The first phase of the feature, Trace Path, enables seeing on the map the path that was traveled. The second phase, Record Path, turns Trace Path into a recorder that can be used both to trace a path and record it. This phase, is to add functionality which would be useful beyond a basic recorder, addressing the most common use cases for recording. **Problem Statements** - Very little data is displayed about the recorded path, and no statistics are available. A significant amount of data is collected during the recording, but it is not displayed, and no stats are calculated from that data. Having more information about the recording would be very useful and motivating to see. - A recorded path cannot be edited after it has been recorded, to remove unnecessary parts of the recording which would not be useful, for example the part before a hiking trail starts, or after the hiking trail ends. - Stats for a trail recording could be inaccurate if there are stops being made, for example for lunch. This gives an inaccurate view about the trail time and other stats. **Use Cases** _Stop Button_ - Stop for a longer time (e.g. lunch) and pause recording to save battery don't record side trips to keep focus on the main route - Don't record particular sections / side trips for privacy reasons - Exclude loitering time from the stats **Ideas** The suggestions in the comments about potential functionality to implement in this phase. As the process proceeds, these will be defined in more detailed and scope for this item will be determined. - Activity recorder: - Activity type selection - Stats (time, distance, speed, max speed, elevation gain/loss, etc) - Pause button, to be able to pause a recording, for example for lunch, and then later continue. - Edit the start and end point of the recorded path. When tapping and selecting the track on the map its name, start and end points can be edited (dots/arrows that can be moved on the map?), and track information can be displayed. - Path showing different colors based on speed/pace which is user defined. - Save a track at any time without stopping recording, for example, by highlighting it on the map, like a lap tracker. **Design** https://www.figma.com/design/5R5LmdM6L4GyfWjSrtlFqZ/OM-Track-Recoding-by-KK?node-id=0-1&t=jki69EK76A23HP8S-1

👍 3 😕 1 ❤️ 1

This repo is archived. You cannot comment on issues.