Skip to content
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

Reprocess older workout weather data #480

Open
Dryusdan opened this issue Jan 14, 2024 · 5 comments
Open

Reprocess older workout weather data #480

Dryusdan opened this issue Jan 14, 2024 · 5 comments

Comments

@Dryusdan
Copy link

Hello 👋

First, thank you for this amaizing project, I can now download all of my bike data without any dependent service.
Actually, this issue is not an issue but a question.

I fetch and download all of my bike workout from Garmin (I made a little program, may I tall about it later (it's open source but in earlier state)) and I generate too many requests on visualcrossing.
My account was "banned" from visualcrossing for overcharge after multiple HTTP code 429, I receive 401. I can "unblock" my account, but all of my acitivies sended haven't weather data.

Is there a way to reprocess all workout without weather data ? :)

Thank by advance :)

@SamR1
Copy link
Owner

SamR1 commented Jan 17, 2024

Hi,

Thanks for your feedback.

For now it is not possible via the API to reprocess workouts to get weather data or recalculate some values like max speed for instance (only few values can be updated).

Maybe one workaround is to add a pause between workouts imports to avoid exceeding Weather API rate limit.

@Dryusdan
Copy link
Author

Hum, okay.

Okay, I will add a rate limit for import in case of weather is enable on fittrackee instance. Thank :)

@SamR1
Copy link
Owner

SamR1 commented Jan 18, 2024

is there a lot of workouts to reprocess?

@Dryusdan
Copy link
Author

Approximately 1400 ^^ (I forgot to remove my weather key on my dev instance 😅 )

@SamR1
Copy link
Owner

SamR1 commented Jan 20, 2024

yes, for bulk imports via scripts, the other solution is to temporarily remove the key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants