-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong decimal separator when importing activities via Strava API #88
Comments
I just saw another error in the screenshot: the timestamp of the activity is wrong. I suppose Strava stores the time in UTC, while the activity was recorded using CET, i.e. it started at 10:19 am. |
I screwed around with m and km as units. I think I've fixed some of these issues but haven't published those fixes yet. I'll look into that. The time zones are another issue. I convert everything to UTC. But I have started to think that this doesn't make so much sense. What we want is local time zone, we don't want to compare absolute times with each other or convert to different time zones. So I think I will change everything to timestamps that are in local time and not time zone aware. |
Done in 0.19.0. |
I just updated to the newest github commit and get the following error with Strava API import
|
Version 0.20.0 is released you can update and try it out. If the issue persists, please reopen this ticket. |
I imported all of my Strava activites using the Strava API setup into a cleaned cache. Unfortunately, the distance information of the activities is identified wrongly, supposedly due a wrongly used decimal separator in the data. (see issue #86 pointing in a similar direction).
The text was updated successfully, but these errors were encountered: