Recently I noticed that speed/pace data shown by Ascent for fast segments (and also for max speed/pace) are notably lower than they should be. At the same time, speed/pace data shown by GTC for the same segments (and max speed/pace) look more like they should be.
It seems that Ascent simpy takes data from the activity data file, while GTC apparently recalculates speed from coordinates and time. Probably Forerunner 405 (that I use) is not very good at determining speed, and GTC "knows" about it and recalculates speed, while Ascent doesn't.
If this is correct, it would be great if Ascent recalculated the speed too. If not, there should be some other reason and a way to correct speed/pace data in Ascent.
P.S. Checked two other similar programs, one of them shows same values as GTC, another one -- same as Ascent. Interesting...