UrbanBiker
UrbanBiker copied to clipboard
Sublimis
Strava upload: Time in motion same as total time
<=v 7.105 Recorded trip times are differentiated into total and time in motion. But when exported into Strava total time is inserted for both fields. Time in movement is ignored.
Hi, we cannot replicate this issue.
Does the info on this page help? https://support.strava.com/hc/en-us/articles/115001188684-Moving-Time-Speed-and-Pace-Calculations
(especially the part that lists exceptions to the moving time rule, eg. "If a run activity is tagged as a race, we will use elapsed time")
Please let us know. Thanks for the feedback!
Well, the problem persists. The Strava help page didn't help. I use my bike at home without GPS, it's tagged as training, I pause manually. There are clearly two different times: time overall and time in movement. If the training is exported to strava, there is only one time for both data fields and it is the total time including breaks. Unfortunately, this renders all other values unusable: average, FTP, etc. It looks to me as if Strava calculates stupidly from start time to end time and completely ignores automatic or manual breaks. Perhaps it is necessary to fool Strava regarding end time by subtracting pause times before data export.
This should be fixed in the new v7.106, but please let us know after you confirm.
You are right about the way Strava calculates moving times, but this is probably not just their fault. Since this is the indoor training, they can't calculate speeds using GPS locations to determine when the user was pausing (based on some minimum speed value), because, obviously, there are no GPS locations. And there is no other way for our app to explicitly tell Strava what the moving time was. Whether this is a bug or a feature on their end is hard to say, but the workaround was pretty obvious. UrbanBiker will now create a new "segment" in a track when you pause/resume, so Strava knows not to include time between segments even without GPS coordinates.
After a bit of googling, we found this: https://communityhub.strava.com/t5/ideas/gpx-import-ignores-trkseg-xml-tags-thus-violating-gpx/idi-p/19706.
This proves that what you (and users from the link) are experiencing is actually a Strava bug. Unfortunately, there's nothing more we can do about it and we suggest you put more pressure on Strava developers to speed things up.
Thanks for the feedback!
OK, thank you!
Daniel
Urban Biker @.***> schrieb am Di., 30. Jan. 2024, 02:09:
After a bit of googling, we found this: https://communityhub.strava.com/t5/ideas/gpx-import-ignores-trkseg-xml-tags-thus-violating-gpx/idi-p/19706 .
This proves that what you (and users from the link) are experiencing is actually a Strava bug. Unfortunately, there's nothing more we can do about it and we suggest you put more pressure on Strava developers to speed things up.
Thanks for the feedback!
— Reply to this email directly, view it on GitHub https://github.com/Sublimis/UrbanBiker/issues/195#issuecomment-1915871839, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGCDRDVD4ZEOFHHDRUWNSK3YRBB6BAVCNFSM6AAAAABBWX2W46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVHA3TCOBTHE . You are receiving this because you authored the thread.Message ID: @.***>