This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GCOverrides

While it is rather complicate to make Garmin responding to bug reports or to feature requests regarding Garmin Connect Web, it is often possible to make the changes ourselves, locally. A feature of the Chrome browser, called Local Overrides, allows it - you can customize not only the look of the pages, but in some cases, and to certain extent, even the functionality.

When reading the forums, I saw many requests, where the overrides could be used, and decided to test whether it could be done. After some testing I decided to share the results with the community. 

The installation of the overlays is easy - it is sufficient to download the file archive, unzip it into a folder, and then assigning and enablig it in Chrome DevTools. Detailed description of the functionality, and step-by-step installation instructions are available on GitHub. The only inconvenience is, that to keep the GCOverrides active, the DevTools pane or a window need to stay opened. The best way of doing so, is detaching them from the current page as a separate window, and minimizing them.

Recently, the Local Overrides work also on the latest Microsoft Chromium Edge.

The installation process is explained in details in the README file

Current Features (GCO v1.20)

  • Weight - 6 Months Report - brings back the 6 Months report plotting all weight data within the 6 motnhs period (not only monthly averages like the 12 Months report does) Note: as of 2020/04/03 I noticed a new look of the Weight page in GC, and this feature of GCO does not work with it. However, since it still seems to be just an intermediate version, suffering some problems, I'll wait till Garmin fixes the bugs, before trying to add the 6 months report again.
  • Activity Overlays bugfix - adds missing overlays and their labels on zoomed graphs on the Activity pages
  • Floors per Min bugfix - fix of the incorrect pace on the native GC Floors Climbing Activity page 
  • Configurable Sleep Goal - see the chapter Setings in README.md for instructions
  • Conversion of Calories to kilojoules on the Calories In/Out page and on the Dashboard; needs to be enabled in the GCO Settings
  • Adjustable Y-axis on Graphs - turns the majority of graphs to have adjustable Y-Axis (with the help of selecting a rectangle of the current graph). Please note, that due to the compression of JavaScript files and the use of numeric chunks in GC, this feature may require frequent updates, and/or may not work for everyone. Searching for a more stable hack.
  • Panning of Graphs - the user can press the Shift key and drag the mouse in order to pan a zoomed graph (same limitations as at the previous feature)
  • Exportable Graphs - additional Export menu at zoomed graphs allowing the export of graphs as images or PDF
  • Enhanced Graph Tooltips - Distance added to all time-based activity graph tootips; improved formatting of tooltips on zoomed versions
  • Hiding Golf - optional hiding of Golf from the Side Menu and from the Gear Menu;
  • Hiding Model-Based Badges - badges designed only for exclusive watches may be hidden from the list of available badges 
  • Enabling manual date input in Reports - in the native version, on the Progress Summary page of Reports, the date can only be picked from the Calendar. Now you can enter it manually.
  • Diving Distance - information about the aerial distance between the entry and the exit locations of a dive
  • Step Counts for Activities - on the pages of activities of the type Run and Walk, the count of steps done during the activity is displayed
  • ... more to come

For details, please have a look at the CHANGELOG

(I'll be updating the list of features above, when new ones will be added)

  • Version 1.13 - added Diving Distance - information about the aerial distance between the entry and the exit locations of a dive (for example for dives logged with Garmin Descent MK1)

  • How do I enable it? I what do I have to edit? 

  • The installation process is explained in details in the README file. Thanks for the query, I'll have to edit the initial post to make it clearer.

    https://github.com/truxoft/GCO/blob/master/README.md#Installation

    Edit: should you encounter any problems, let me know. It may help improving the instructions.

  • Hey Trux,

    Did you notice that the override to display the 6 month graph died with the new format? Also, although this isn't related to GCO Overrides, the weight graph now shows multiple values for each date instead of just the last.

  • Yes, I know. They changed the weight page significantly, so I am not sure whether trying to add back the 6 months report is still needed, since the Yearly report is already finer than it used to be. However, I did not even try doing any adjustments on the weight page, since it looks like they are still working on it. For example there were issues with entering new weight-ins in kg (it was entered as if it were in lbs). For that reason I am waiting a bit until there is a stable version, and will look then whether I need to redo some of the adjustments in GCO again.

  • While the 1 Year display is a bit more granular, it still doesn't serve those (like me) who want to know how their last weight fits the trend. For example, one day last week, my weight was the lowest in 6 months. Unfortunately, it didn't last long.

  • I will have a look at it, but it is possible that with the recent changes the 6 months report is completely gone, so am not quite sure whether I'll be able to help with the overrides

  • I suspect you're right.

  • I suspect you're right.

    BTW, do you really need to see the detailed graph over 6 or 12 months? Isn't the current 4 weeks report already sufficiently long and detailed to see the trend? (you can even repeatedly shift it to the previous 4 weeks, if needed, with the help of the navigation buttons)

  • This is my challenge:

    In winter, I can gain up to 10 pounds because I don't ride my bike from about November until around the end of March. Then in summer, during the biking season, I lose the weight gradually. 

    If I can pinpoint the reason it's because during a day when I don't bike, the amount of calories I burn in activities is 500 to 700. When I bike, I regularly burn 2,000 calories or more per day. 

    So when I monitor my weight, I always compare to where I was in the previous season. If I had a granular graph for 12 months or more, it would be even more relevant.

    In fact, I keep a record of my weight everyday in an Access database. Because of the graphs available in Connect, I haven't needed to create a graph in Access but it will probably come to that.

    BTW, I do something similar with distance cycled or run. I have a YTD report in Access for distance cycled and another for runs. This year, I've cycled 344 kms. Last year, I cycled 148 kms by this date.