• Replies 6 replies
  • Subscribers 17 subscribers
  • Views 721 views
  • Users 0 members are here
Options
Related

Is it possible to access distance to destination during an active navigation session?

9322612
over 2 years ago

My idea is creating a datafield that shows a more intelligent ETA by calcualting it from an averaged pace in movement that does not include pauses into it's calculation (like the stock ETA darafield from Garmin). This is something that annoys me during hikes since the ETA often gets unrealistic after resting.

However I can't find anything suitable in the API documentation.

  • over 1 year ago

    I've done exactly that in my Race Guage Data Field. It does three things really well. One is the ETA calculation. I use Avg Moving Pace, with a small assumed stop per hour to account (a couple mins) and a small degradation in expected pace per hour (slight reduction) based on your current avg and the hours remaining. It works really well. You specify your intended distance, and it calculated the projected finish time and duration. Or you enter your intended time (like a 12 hr or 24 hr race) and it'll calculate your projected total distance. I'm working on adding a 3rd option, which is to use Garmin's Distance to Destination for a loaded route, but there are lots of corner cases that make that challenging. I'm working thru those. Like riding to the start, going off route and then back on, entering the route at some point other than the start, etc. I hope to have that working in about a week. Naturally, if you do stop, it'll recalculate the ETA when you start back up, accounting for your stop time.

    The other two functions leverage touch screen tapping to allow you to enter your fluids and calories, and it compares your consumption against what you should have consumed (which is informed by HR Zone and Ambient temps, and a bit by elevation). And it provides a dial to show where your power (watts) are in relation to your desired range of power you'd like to generate... this also slowly reduces over the hours, which I've modeled based on analysis of highly trained endurance cyclists. You can set a User Setting to cause the reduction over time to be more aggressive or even flat (no reduction). The dial is a visual to keep you in your sweet spot.

    apps.garmin.com/.../11c2aa49-e191-472a-b3d1-d3ccf4fa8083

  • over 1 year ago in reply to DaveBrillhart

    I've done exactly that in my Race Guage Data Field. It does three things really well. One is the ETA calculation. I use Avg Moving Pace, with a small assumed stop per hour to account (a couple mins) and a small degradation in expected pace per hour (slight reduction) based on your current avg and the hours remaining. It works really well. You specify your intended distance, and it calculated the projected finish time and duration. Or you enter your intended time (like a 12 hr or 24 hr race) and it'll calculate your projected total distance. I'm working on adding a 3rd option, which is to use Garmin's Distance to Destination for a loaded route, but there are lots of corner cases that make that challenging. I'm working thru those. Like riding to the start, going off route and then back on, entering the route at some point other than the start, etc. I hope to have that working in about a week. Naturally, if you do stop, it'll recalculate the ETA when you start back up, accounting for your stop time. In the last portion of your ride, it uses an Avg Pace over the last few minutes, rather than your overall avg pace. This helps improve the ETA in case in the last 10 miles or so there is a big tail or headwind, or a climb, etc. Which causes your final pacing to be significantly different than your overall. Thre is more secret sauce, but that gives you an idea.

    The other two functions are fueling and power. Fueling leverages the touch screen to allow you to enter your fluids and calories, and it compares your consumption against what you should have consumed (which is informed by HR Zone and Ambient temps, and a bit by elevation). The power dial shows where your power (watts) are in relation to your desired range of power you'd like to generate... this also slowly reduces over the hours, which I've modeled based on analysis of highly trained endurance cyclists. You can set a User Setting to cause the reduction over time to be more aggressive or even flat (no reduction). The dial is a visual to keep you in your sweet spot. I have other things like a live weather view that shows the wind direction and speed, etc.

    apps.garmin.com/.../11c2aa49-e191-472a-b3d1-d3ccf4fa8083

  • over 1 year ago in reply to DaveBrillhart
    DaveBrillhart said:
    I've done exactly that in my Race Guage Data Field

    If you read between the lines ("during hikes"), OP probably needs an app that works with a watch, not just Edge bike computers.

  • over 1 year ago in reply to FlowState

    Right, so I gave him some tips on my logic to help him think thru some of the features that help make my ETA function work well.

  • over 1 year ago in reply to DaveBrillhart

    Fair enough but your comment read like a detailed ad for your data field and didn’t even acknowledge the stated use case of hiking. For example, I don't think wind direction and a power gauge are relevant to hiking at all.

    Not to mention the question in the OP was "Is it possible to access distance to destination..." and implicitly, if so how? If I were OP, I would read your comment and realize, yes, it's possible to access distance to destination, but I still wouldn't be any closer to knowing how to do it.