Name: OCD HR-ETA (Heart Rate-Estimated Time of Arrival)
Rating: 4.7 (3 reviews)
Author: OCD

DF for bikers

Why and What? Using the bike computer I miss two features: to check in a glance all related with HR (current bpm, Zone, %HRMax…)  and to have an estimation about the time I need to spend to reach certain distance to fit my available time with my workout time on the fly

Basically, the data field has 2 main functions or sections:

=====Time estimation section (upper)
On top (first row) it shows the current time (TOD). 24h format

Left side of the second row it shows the ETE (Estimated Time Enroute). It means, the time needed to reach the next distance goal (blinked on pause). Right side shows the distance left to reach it

Distance will be auto increased as it will be achieved. These are: 30,50,60,70,86,90,100,120,140,160,180,200,300 miles or Km according watch configuration

Third row shows the main section value: ETA (Estimated Time of Arrival). It's the local time when the next distance goal will be reach

There're 2 methods available to calculate the ETA (that can be set on the properties page):
  - Based on workout average speed
  - Based on the last x distance rode to find the average speed. It's necessary to ride the first Km or mi to obtain an early estimation (meantime ETA & ETE will have no value). This last x distance could be set in the properties page (from 3 to 25 mi/km. 15 by default)

Other approach to estimate the ETA (i.e. based on current speed) doesn’t make sense for me

Background of this section will change according watch configuration for the activity

===== HR section (middle and lower)
As the data field is intended for bikers, we only have a moment to read the information before to keep looking at the road. This way, this section shows the main HR values (bpm, %HRMax and zone) making use of the Garmin HR zone colors, helping to know current HRZone at a glance. Furthermore, bpm and %HRMax numbers are big to help to read it quickly and easily

Left, first row: current HR in bpm
Right, first row: the HR percent regarding the user max HR threshold (max Z5) or according Karvonen's method (taking into account the user max HR and the user Resting HR)
HR Zones and Resting HR are obtained from Garmin user profile. HRZones for cycling if any or default profile.  Resting HR always from default profile due Garmin limitation

Second row: centered, the HR Zone we are; the max bpm reached on the workout at left side and the Strava Live Suffer Score (SS) at the right side, changing color according Suffer Score scale by Strava (tough=green, extreme=yellow, epic=red)
Suffer Score is recorded in the activity as a graph

On the middle bottom, is the graph with time spend in each zone wrapped by the time spend in the current zone (left) and the time percent regarding the total (right)

Although Z0 is not considered in the graph it is used to calculate the zone time percent. Meantime we remain in this zone, section background will be black

It is possible to set to show the HR Zones Threshold values that are in use (at the middle centered). Useful to check values read from profile or watch (depending model device)

------------- Considerations -------------
As data fields have a very limited watch memory available to run and as I don't want to find me in a situation where a data field fails and the hole session recording is lost as consequence, I've pay attention on all development details such code optimization, memory consumption and what info/labels to add (removing info no relevant such certain prefix/suffix or available out-of-the-box data such speed, distance, elevation, grade or whatever value that could be easily added out-of-the-box on other data screen)

NOTE: This data field need all screen size, so it’s only well-drawn for 1-FIELD LAYOUT. Otherwise the content becomes unreadable

Use it as your own risk. ;-)

If it's useful to you and you want to express your gratitude sending me a DONATION you can do it @ https://www.paypal.me/ISAFP