For fun and learning and my personal use I wrote a simple data field to use on my Epix when I bought it nearly 2 years ago. It was to get more data on a single screen. The version of the SDK at that time didn't have distanceToDestination so I laid out the field to fit the top spot on a 3B layout and since I was mostly hiking using a route I would put the native distance remaining and native ETA in the bottom two fields. Well I bought a Fenix 5x this week and my first task was to change up the layout to better fit a round screen and while doing that I noticed the info.distanceToDestination is available on it. I double checked it with the 'has' functionality and also tested it using the simulator. So I would love to make my datafield fullscreen but I'm left needing to calculate ETA. Does anyone have any thoughts on the algorithm Garmin is using natively for ETA? Does anyone have any suggestions? A simple solution could be to use distanceToDestination / averageSpeed. But my trips are 10 miles give or take and over that much distance and time the overall average may not be a really good figure to use for ETA. In other words I'm wondering if a 'last 10? minutes average' or something similar may be a better indicator of speed to calculate ETA. Say the average speed of the full 6 hours of hiking is 1.5 mph but for the last 30 min it has been 2.5 mph. Obviously it would be nice to see that increase in speed decreasing the ETA. I'd really appreciate any suggestions.
In the simulator I can set the distance to destination in the Set Navigation Data and the value works as expected. I went out for a walk navigating a course i quickly created in GC and the native distance remaining worked as expected but the info.distanceToDestination always had zero.
