Tracklog datapoints [Local time, speed, altitude, export CSV]

[Yannick van Vugt 1]

Feature request regarding tracklogs

A great addition would be the ability to have more data within tracklogs, as it currently only tracks your route and calculates your avg. speed based on start time, end time and recorded distance.

If each recorded datapoint also contains:

• Local time
• Current speed (based on GPS data)
• Altitude (based on map or GPS data)
• Direction / heading "NW (312°)"

Then, based on this information, even more data could be displayed.

Track information (additional information)

• Top speed
• Elevation gain/loss

Track point hover

• Time
• Speed
• Heading
• Distance from start
• Time from start
• Acceleration
• Vertical speed
• Route progress (%)

Since the track information is currently shown on the left, it would be great if clicking on an item would show the corresponding point on the map, or have matching color-coded markers on the map by default.

Hovering over the tracked line could display an information panel in the bottom-right corner of the map, showing the data for the selected point.

Possibly a dropdown menu with the options to:

• enable a colored line, based on your speed or altitude.
• select information shown in the information panel

There would be a lot of data to play with and make tracklogs way more interactive, interesting and fun, rather than only using the data to create new planned routes.

If we can also export this data to a CSV* for example, the data could also be used in other ways. Depending on the interval**, it could also be used as an overlay for action cam footage.

*The CSV would contain all kinds of columns, for example:

• elapsed time from start (in milliseconds)
• UTC time (epoch, or another usable standard)
• local time / timezone offset
• longitude
• latitude
• altitude
• speed
• heading in degrees
• distance traveled from start
• route progress (%)
• gps accuracy (m)

**Add the ability for the user to choose an interval, default or shorter, depending on how the data would be used. The default interval would remain suitable for normal MRA track logging. Users could optionally select a shorter interval, ranging from the default setting down to 16.67ms (60Hz)/20ms (50Hz)/100ms (10Hz), for example when the data is intended for an action cam overlay. (This uses more battery, and I know it will also mean more backend storage, but it's just an idea. Maybe make the high-frequency data only available for a month and then automatically reduce the data to the default MRA interval)

The main feature request is the additional track data, hover information panel, map markers and colored track visualization. The high-frequency logging and custom interval functionality are intended as optional extras.