Some users contacted me saying that when they timestamped their files, they would get a 0 or 1 second activity - even if they had thousands of points. I looked into it and found that people have been using original source files with 1 second recording turned on for their source files, meaning a very high point density.
The problem here is that the minimum duration from point-to-point is one second. If a user tries to timestamp a file with a speed that is faster than the original activity, the duration from point-to-point will calculate out to less than a second. Previously, GOTOES handled this by rounding the time downwards, meaning that there was a 0 second interval for many or all of their points. This would create an unusable file!
To solve this, GOTOES now looks at the point-to-point time, and if the calculated duration to achieve your desired speed is greater than zero seconds, but less than one second, the time will ALWAYS be rounded up to one second.
The result is that you will at least receive a useable file. The negative is that you're going to have a speed graph that looks jagged... especially if we are having to round up a lot.
There are two solutions if you are not happy with your Speed Graph:
1) Use a desired speed that is more compatible with the source file. If you have an activity that used one second recording and you went 12 mph on average, do not try to make the activity go faster than 12 mph. You shouldn't be increasing speed anyway.
2) Use a source file that has been "thinned out." Route Files almost always have a lower point density than activity files, so you can use a Route File instead of an actual activity file. If your only option is to supply an activity file and that file had one-second-recording activated, use GOTOES to "thin" out the file by discarding track points first by using the "Discard x Trackpoints" Feature. Then come back and apply the desired speed.