I've used the "Ski" app for tracking 2 yesterday and today ski days with my new VA3. I can see what Garmin is trying to accomplish with this app, namely tracking the runs there the descents, then not tracking the lift rides. Nice idea, but it is grossly flawed. For every run, the altitude recorded at the end of the run has a knife edge drop. While I am an expert skier and don't mind the occasional cliff, there certainly is not one at the bottom of every run, especially not a 600 foot cliff. The issue with it is it creates a grossly wrong elevation profile and total vertical count at the end of the day. Today was off by over 5000 feet due to the cumulative addition of the errors across a day. See the elevation profile images attached (Note the vertical wall for ascent is the positive artifact of not tracking the lift ride up, just capturing the bottom and the top of the lift). This issue makes the numbers useless. Why bother if the data is so fraught with failure.
Is Garmin aware of how poorly this logic in this App is programmed? Granted the product is likely developed in the flat lands of Kansas, but one would thing they'd test it's operation at a ski area before putting on the watch.
In the future I'm just going to let the watch run using the Bike profile and let it track all the time. At least the information obtained will be accurate. ciq.forums.garmin.com/.../1441902.jpg ciq.forums.garmin.com/.../1441903.jpg
