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

What data fields for trail running?

Fredrik_Coulter
over 5 years ago

I'm starting to create custom data views for various events.  I've got a 12K trail race in a week, so I'm thinking about the trail run widgets.

I'd like to create a screen that displays the most useful data.  For me, the top item needs to be the heart rate zone data field, with the number and the range.

I think that Distance, Pace, and Timer would also be useful.  But that leaves one unassigned data field.  And I may be wrong about what data fields would be best for a trail race.

What data fields do you use when running in the woods?

  • 0 over 5 years ago

    They sound like good fields to have. Although you may want to consider lap pace if GPS issues in the woods makes instantaneous pace a little "noisy".

    My approach to screen design (especially when racing) is for it to be as clean and as uncluttered as possible, and only fields directly related to performance and navigation. This makes it easier to see while running, and reduces cognitive load. If that means not using every field available, that's just fine by me. Secondary information (like battery %, time of day, etc) goes onto another data screen, that I can scroll to if I need to.

    Elevation, distance to next waypoint, average pace are other ones to consider, depending on terrain, ease of navigation, and whether you are aiming just to compete or targeting a specific goal time.

  • 0 over 5 years ago

    As per mcalista, you might consider not trying to squeeze everything into one screen (in my case age and eye sight make this useless anyway).  I tend to adjust my options based on the race type (distance, terrain type, need for navigation support, cut-offs, aid stations etc).  I don't use HR when racing and even find instant or lap Pace can be limited value when the terrain is really tough/hilly.  For some specific races I have built custom data fields using AppBuilder to, for example, estimate time remaining to aid stations/cut-offs.  As mcalista ends his post, lot depends on your goal for the race but suggest you keep it simple.

    A feature request (that I have submitted) is to be able to tag specific data fields for auto scrolling while skipping others unless you actively select to go through them manually (then return to auto scrolling).  This would allow two or three main, limited data screens to autoscroll  (example HR, distance/time) while having other less likely to be used pages available.

  • 0 over 5 years ago

    i would also consider 1 screen having the total ascent / total descent datafields. if there's a bit of a climb, you might want to know how to pace yourself according to how much climbing is left ;-) 

  • 0 over 5 years ago in reply to tsofron

    Living and racing in  Florida, ascent and descent are more theoretical constructs than actual measurable numbers.  That's what happens when you live on a giant sandbar.