Syncing from Garmin Connect to Runkeeper uses "elapsed time," not "moving time" about tapiriik HOT 14 OPEN

The Garmin Connect integration actually does support moving time, in addition to elapsed and timer time. It's just that other sites have different interpretations of these names, and most do not support all three. I don't know which service your activities are getting synchronized to where you think the times are incorrect on, but if you can tell me I'll look into it.

from tapiriik.

It looks like runkeeper imports from garmin connect used the elapsed, not moving time. My activities are public, so feel free to use them to debug: Username jacobrothstein on both

Edit: It's just runkeeper, not runkeeper and strava.

from tapiriik.

I'm having this same issue. I've emailed support but haven't received a response. Any updates to when this may be resolved?

from tapiriik.

This is happening to me, too!

from tapiriik.

The same issue applies from Strava to Runkeeper synchronization, i.e. the "elapsed" time from Strava is synced to show as "moving" time in Runkeeper.

Here is an example activity that was synced:
Strava: http://www.strava.com/activities/187886603
Runkeeper: http://runkeeper.com/user/dickolsson/activity/424952571

from tapiriik.

Created a separate issue for the Strava -> Runkeeper problem: #52

from tapiriik.

I'm new to tapiriik, and I've just encountered this same problem. Syncing from Garmin to Runkeeper posts my "elapsed time" in runkeeper rather than "moving time." Noticing this thread is about 4 months old. Has there been any movement here? Is this still an outstanding bug? Seems pretty substantial to me. I routinely pause/stop my garmin watch when runnign -- at street lights, getting water, etc. Thanks for any update.

from tapiriik.

@cpfair anything new on this issue? As soon as this is fixed I'll gladly pay the yearly fee.

from tapiriik.

Any news on this? - Sync from Endmondo (uploaded from Garmin connect) to Runkeeper uses elapsed time (frustrating).

Would gladly pay if this bug is fixed!

Also, once fixed, how to refresh the incorrect times on runkeeper

from tapiriik.

I never heard anything in response to my inquiry.

Sent from my phone.
On Mar 11, 2015 7:41 AM, "Peter Atkins" [email protected] wrote:

Any news on this? - Sync from Endmondo (uploaded from Garmin connect) to
Runkeeper uses elapsed time (frustrating).

Would gladly pay if this bug is fixed!

Also, once fixed, how to refresh the incorrect times on runkeeper

—
Reply to this email directly or view it on GitHub
#16 (comment).

from tapiriik.

@cpfair - looking through the thread, this bug has been outstanding for several months now, this is a significant issue affecting recording of times correctly, - (Import from Garmn Connect in to Endomondo handles elapsed times correctly). Tapiriik sync between endomondo (with correct times) and runkeeper does not - any updates on when this will be fixed?

from tapiriik.

Another user having the same problem here. I am afraid that this will never be resolved...? I too contacted the developer, but no response up untill now. I am glad to hear I am not the only one having this issue though, although my sync is the other way around. I guess that explains what I am seeing.

My imported activitities from Runkeeper into Garmin Connect show gaps in de SPEED/PACE sections. All other data is fine. But the gaps make it so that Garmin Connect registers my best paces as 0:38 and such. I am no way near that fast (not is any other human being). This messes with my records, achievements and so on.

I too would love a fix for this erratic behavior.

from tapiriik.

As far as I can tell, RunKeeper's "duration" display is timer time, not moving time, by design. The closest they get to "moving time" is the auto-pause setting in their app. A year ago I wasn't eager to come up with a workaround for this, but my opinions on the matter have since softened. I just pushed a change (b2e1f9c) that adds an option to simulate auto-pause; turn it on at http://tapiriik.com/#/configure/runkeeper. It will add pause/resume points at (hopefully) reasonable locations to match the timer time to the moving time. This will only work when the moving time is known beforehand (e.g. activities downloaded from GC) - it doesn't attempt to calculate it from scratch, merely to match the known-correct value.

As for RK to GC - RK does not provide any data stream for speed, so if you're seeing a speed/pace graph on Garmin Connect, it's Garmin Connect that's generating it, and I'm not sure what's going wrong there.

from tapiriik.

looks like this problem is still not solved more than 1 year down the road. I'm also experiencing the same issue. My GC data is correct but it will screw up my runkeeper data if there is a pause. i don't mind small inaccuracies but when i pause for 10 mins (like when it rains real hard) - my whole run statistic is screwed up real bad! Anyone has a workaround yet?

from tapiriik.