Name: Lap Max Speed and Floating Average of Max Speed
Author: hopet

Simple Garmin Connect IQ app to enable per-lap maximum speed for Garmin Fenix watches. 

Data field has been primarily motivated by downhill sports, namely downhill/resort skiing. Standard Fenix Ski mode does this partially automatically, but the automated detection of downhill skiing and stopping for uphill chair lifts is not always perfect and in smaller resorts with lower elevation differences one often needs to use other ski modes (such as backcountry or XC skiing) to get meaningful recordings. Then the per-lap maximum speed is not available among standard data fields. 

When writing a custom data field, I took the opportunity to implement also averaging maximum speed over user-definable window, so that one can get more stable readouts of maximum speed. This maximum speed floating average is shown next to the instantaneous maximum speed.

## Description
Current implementation is very minimalistic data field generating 5 numbers:
- maximum speed (typically checked once per second) in the current lap (top left)
- maximum speed over floating window (10s by default) in the current lap (bottom left)
- maximum speed (typically checked once per second) in the previous lap (top right)
- maximum speed over floating window (10s by default) in the previous lap (bottom right)
- length of the floating window (bottom middle, configurable via data field settings)

Note that for some screen layout, the last lap values and lenght of the floating window is not be shown.

This data field makes for the lack of per-lap maximum speed available among available speed data fields on the Garmin Fenix series. 10s floating averaging window has been added to make for more stable measurements. Since version 1.3, these are stored into the FIT recordings, too.

Known issues: 
- On some older Fenix 6X firmwares, Backcountry skiing app (by Garmin) unfortunately uses Lap key for switching ascent/descent modes and does not generate new lap. Current firmware 20.30 seems to work fine.
- New dynamic layout may run out of memory on Fenix 3/HR devices, which are limited to 16kB. Needs further investigation if we have to disable compatiblity with these.

Other bugs and issues can be reported via GitHub Issues.