-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Uploading using the GPX/TCX format #139
Comments
Well, I think my post wasn't well thought out. I now realize that uploading a previous activity that I have downloaded ... just creates 2 duplicate activities. (oops). I'll keep this open for a couple of days hoping that someone will know how to update Garmin .. otherwise I'll close it or @cyberjunky . |
Hi @bobgott, Having played with this myself a bit, not uploading, but downloading, it is worth knowing that the info you can download from Garmin via their API comes in two separate entities (formats):
Both can be downloaded and read via this library: https://github.com/petergardfjall/garminexport. The activity name is in the JSON file in a field called 'activityName'. I don't know about UPloading info to Garmin Connect via the API, not sure if that is possible, but in case it is, you'd need to be manipulating the JSON file that contains the activity metadata, changing the activityName field and uploading. As it is in a JSON, parsing/modifying is straightforward enough. Hope this helps, |
@dan-p-p I fear my goal might be a lost cause. |
Closing since it has become stale, if someone has new information please open a ticket. |
I'm hoping to get some insight into
upload_activity()
before I start my project. My goal is to update the value held by 'activityName', but I also understand that updating is not the main focus of garminconnect.I think I can achieve my goal via
download_activity()
with the GPX or TCX format (it appears you can't download in FIT format), modify those fields that interest me, then upload the modified file viaupload_activity()
.Does this seem like a reasonable approach? Any merits one way or the other with regards to GPX/TCX format?
The text was updated successfully, but these errors were encountered: