Sure. Here’s an example of what it looks like, when I have a run-counter app, to push data to the site (either MovesCount, or Sports-Tracker).
https://www.sports-tracker.com/workout/petegrey/5c6dd27f0f3e495dc8a0bd41
If I do this w/o the counter, it’s just a bunch of random data on the mountain, it includes the chairlift rides and everything, as one “big run”.
I guess you could manually use laps, to separate things, but remembering to do this (we are in 2019, right?) is inconsistent, and can be unpleasant, say if it’s 5-degrees-F, on a day (usually involves taking off a glove, shoving my coat and other layers out of the way, to push a lap button).
I have a couple of custom-screens in my Alpine Skiing, which is really handy for at-a-glance stats, for things like number of runs, descent-per, etc (which Suunto obviously excludes in the Alpine skiing screens, because it has no “run” concept on the Ambit3 skiing mode).
I use a similar set of screens, and an app, for group sprint sections on when riding (road cycling), so I can see how I’m doing, at-a-glance, on a particular day.
Removing all of this pretty much means my watches are non-functional, for my use, and they either become auction items, or landfill items (which it seems like the Ambit2 Sapphire is, regardless).
Edit: I should mention, too, that it took me over an hour, with SA, to get my Ambit3 to sync a handful of moves (about 10/20), at which point it failed outright, and said it was unable to sync further (despite multiple retries). This is on a VERY fast phone, with an 845 chipset, Bluetooth 5.0, screaming-fast data pipe, etc, that can sync my cheap-o Garmin tracker I wear to track daily stuff (Suunto resting HR is way too inaccurate to even consider for this), in maybe 20-30 seconds (syncing a couple of days of complete HR/activity/sleep data, in that example).
Edit2: I tried SA, again, and it restarted at activity/move 1/26, and was still there after 8 minutes, when I decided to shut it down. Something is gravely wrong with Bluetooth (sync) on the Ambit3, and it’s questionable as to whether or not this would be an app-side fix, IMO/IME. But apparently that’s about to become the “sync standard”, right, whenever the data-port happens, you’ll have to use SA, going forward?
