Related
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

Why no calculation of VO2max in hiking activity?

Former Member
Former Member over 5 years ago

Hi

Why there is no calculation of VO2max in hiking activity?

In the past, I modified a "standard walking activity" and used it for hiking. Unfortunately, these activities are imported to komoot as "Nordic-Walking"!!! I didn't like it.

Thats why, I now modified a "standard hiking activity" of my fenix 5S. Afterwards, export to komoot worked correctly and it's shown in komoot as "Hiking".

BUT: Now, I've seen, that my VO2max value hadn't been refreshed since 28.04.2019. Someone said, calculation is only done in walking and running activities, but why???

Why can't Garmin calculate VO2 max also in "Hiking". I can't understand... HR+Distance+Elevation and other values are cumulated exactly identically...

It makes no sense for me to go back to a walking activity, as I always have to swich the imported track in komoot manually.

BTW: Pardon for a seconed thread here. I already made a command in another older thread in another section. But but I think, it's better to have a new question here.

  • 0 over 5 years ago

    Not sure is the right forum. 

    Supose you walk in wet sand and then walk in dry sand. 

    For the same distance the effort is completely different.  Your vo2max for the dry sand will be lower. 

    That's why Garmin has activities, that seem similar, that calculates vo2max and activities that do not. 

  • 0 over 5 years ago

    I do know that, for the F5 series and the F3 as well, trail run doesn't calculate VO2max where standard run does, and this is because the watch's programming could not compensate for the elevation changes (which could be coded for) as well as for the greater effort of running on terrain that isn't smooth tarmac (which is probably not fixable, too variable), as jose points out. Users were complaining that every trail run knocked their VO2max values down at first, so the VO2max calculation was cut from trail run.

    I suspect it's probably the same reason for walking vs hiking.

    Have you tried asking komoot if the import can be customised?

  • Former Member
    0 Former Member over 5 years ago in reply to mcbadger

    Thanks for your answers.

    No - I havn't tried asking komoot - but I will do.  EDIT: I've just done Slight smile

    Normally, these problems are "not real" problems...Fenix 5S does normally, what I want.

    (I'm only a small "statistic freak" and want to know the reason, why something doesn't work as expected...)

  • 0 over 5 years ago in reply to jose.cboliveira

    This is the right answer.

    The underlying model for VO2max calcs requires some variables be controlled - flat ground in the case of walking/running, or pavement for cycling. Hence, hiking, trail-running, and mountain biking are not used to provide data for VO2max calcs - they'd skew numbers unreliably.

  • Former Member
    0 Former Member over 5 years ago in reply to Otto-Destruct

    Hi,

    thanks for your exlanations. I understood - so far...

    But an activity "walking" also can be done on different grounds - just as "hiking". The past months I used "Walking with some modifications" for my personal use. I only had to modify into "Hiking with some modifications" because komoot always is importing "Nordic-Walking", which I don't like.

    I always do the same - no matter how you call it in the end...

    So, finally I think, VO2max calculation makes no sense for me and most of all users at all - and I will ignore it in the future completely Disappointed

    Right?