Create route has unrealistic time calculation

Follow

MTJ

• June 03, 2017 14:34

Point Mugu California State Park. Chumash trail from the beach to Mugu Peak is 1.1 miles but is a 1200 foot climb and cannot be done in 21 minutes atleast by average hikers. Please include elevation gain in time calculations.

9

• 

  em

  • June 08, 2017 00:01

  Good suggestion. The formula I know of is 30 minutes per mile plus 30 minutes per 1000' climbed.

  3

  Comment actions Permalink
• 

  ctx

  • June 08, 2017 03:33

  Das ist auch ein Problem bei anderen Routen. Die Zeitfunktion ist noch nicht ausgereift.

  1

  Comment actions Permalink
• 

  MicHuizinga

  • August 23, 2017 11:32

  Yes! Please correct this.
  Since you already have an elevation profile, it's a small step from there to calculate accurate hike times. This would be extremely useful!

  1

  Comment actions Permalink
• 

  mshepherd

  • September 28, 2017 12:49

  Yes!  This is such a simple but useful feature!  As is, time calculations are pretty much useless for anything but walking back to your car on a flat road.  They could easily be fixed to provide actual value to hikers.  

  1

  Comment actions Permalink
• 

  ctx

  • September 28, 2017 18:52

  Ein Beispiel:

   

  

  1

  Comment actions Permalink
• 

  Paul Beaudet

  • March 12, 2019 17:53

  the 30 30 calculation mentioned before seems like a good idea, but even if we just got the option to set a mph/kph pace in settings for each type of activity that would be a great hold over before implementing something more complicated.

  Being able to put in a speed that I think is reasonable for my group that I'm taking would be a massive time saver. I could just share the route as say that's how fast I think we might go instead of doing the math myself and separately explaining it to potential trip goers

  1

  Comment actions Permalink
• 

  jon.bracken

  • June 22, 2019 16:12

  I'd like to add weight to this. We live in Vancouver and the local mountain trail time calculations appear to use an average of 4.5 km/hour. We average 2.7 km/hour given the elevation gains and terrain that you encounter here. We have enough tourist getting out of their depth in trainers and jeans without giving the impression that things like Crown Mountain can be climbed and descended in 2 and a half hours.

  1

  Comment actions Permalink
• 

  Paul Beaudet

  • June 24, 2019 19:26

  If Gaia could map the elevation profiles to the default trail routes it would be possible to at least show gradient shade change in how the trail is displayed (one of the overlays shows open rock face which is great). From there factoring in elevation into trip estimates should be possible. Far from perfect, but it would be a  major improvement.

    The reason that approach is still inaccurate is that the trail terrain makes changes the estimate. The next step would have to be curated descriptions, with meta-data for the terrain. Trail meta-data would make gaia a one stop shop power house for trip planing. Particularly if the descriptions were downloaded with the maps. Being able to find suitable outs for sticky situations on trail could turn around a bad day or even save a life. 

  I realize that the Gaia team might not want that responsibility on their shoulders. Either in liability or standardizing the perception of difficulty. Which might be why there is some hand sitting on the time estimate issue and more "look we changed where the buttons go!". Honestly I see people on the trails that don't even have paper maps. Expecting people to completely prepared beforehand is a bit optimistic. It can only be their own responsibility hopefully the failures are small and slow. I don't think the possibility of misinformation creates a "should this exist" issue for the app. Its only going to give people the ability to possibly be more prepared than they otherwise would be.  

  0

  Comment actions Permalink

Please sign in to leave a comment.