Gamin importing as ride rather than run
6 watchers
Dec 2019
10:35am, 15 Dec 2019
4,406 posts
|
Windsor Wool
I have the same issue if more data points help? (Embarrassed how often I stop for a rest in my training runs too!) |
Dec 2019
11:11am, 15 Dec 2019
4,292 posts
|
clare1976
I ran with no stops this morning and its come out normal. I have worked it out I think... we pause the watch, it then takes the elapsed time for a split, then taking the min/mile time (time actually moving and recorded), works out how far you could travel in that total elapsed time and then gives a min/mile pace based on that new distance. |
Dec 2019
11:48am, 15 Dec 2019
26,124 posts
|
HellsBells
I have odd splits too - I pause mine to cross roads so I'm not tempted to dash across without stopping and looking properly
|
Dec 2019
5:17pm, 15 Dec 2019
15,667 posts
|
Bazoaxe
Ive just noticed this as well
|
Dec 2019
6:05pm, 15 Dec 2019
1,543 posts
|
Flatlander
clare1976, that is what I surmised. I've been to my Garmin Connect account to see if these oddities are showing up there, but GC doesn't give mile breakdowns like Fetch does so I can't tell. What Garmins are you all using? I am using a 235 with Software: 8.0.0.0. If you are using different Garmins that might suggest it is a GC problem. If you are all using 235s then it might be a 235 software issue. I am going to experiment tomorrow and wear two Garmins, 235 and 310XT, at the same time and import both activities to see if the problems are specific to my 235 or are a generalised Garmin misfunction. I shall report back. |
|
Dec 2019
6:06pm, 15 Dec 2019
15,669 posts
|
Bazoaxe
I am on the 735. It uploads to |
|
Dec 2019
6:07pm, 15 Dec 2019
15,670 posts
|
Bazoaxe
Garmin connect showing splits correctly also.
|
|
Dec 2019
6:29pm, 15 Dec 2019
4,294 posts
|
clare1976
Same as Baz for me. It goes wappy when the watch is stopped mid-run and that specific split then gets corrupted as it then takes the elapsed time and assumes you've carried on running in that elapsed time, but then only shows the correct split time so the distance and hence pace become way out. E.g I paused my watch for 10 secs today for a crossing. The split was 8.43 which was my mile pace when moving. However the extra 10 secs have given me an additional 0.02 distance, which is what I'd have done in those 10 secs at 8.43mm. It then shows 1.02 miles in 8.43 so gives an inflated pace of 8.33mm for that mile. No big deal for that short a pause but 5-10mins pre or post parkrun, or the 40mins I often pause for the gym and the pace goes wild. This seems to be a fetch only thing, It was fine on my run on Tuesday when I had an occasional road crossing so would have seen it then. So it's happened at some point since Tuesday evening. First time for me was Thurs evening as I didn't run on weds. |
|
Dec 2019
6:34pm, 15 Dec 2019
15,671 posts
|
Bazoaxe
I first noticed it on Wednesday. I did 10x0.25 miles. I had to stop for a car on firstctep which was recorded as 0.29 and I wasn’t sure why.
|
|
Dec 2019
6:45pm, 15 Dec 2019
1,544 posts
|
Flatlander
Yes, for me Tuesday's activity was fine, it all started on Wednesday.
|
Related Threads
-
old garmin activities
Jun 2020
-
Zipped GPX Import
May 2020
-
GPS import
May 2020
-
Garmin 310XT
Oct 2017
-
Garmin numpty question
May 2017
-
Multiple activities in one TCX file
Apr 2015
-
Import Training Direct From Your Garmin (wooooh) (:-O)
Nov 2014
-
Upload from Forerunner 310XT
Dec 2012
-
Upload from apple watch
Apr 2024
-
API
Dec 2023
