-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
Strange double track segment in GPX export #15684
Comments
this is actually the first item of your individual route. c:geo stores a route internally by segments, with one segment per item of your individual route. The first segment contains of the route's first item only, then each following segment has the next item as last point of that segment, and the points from the last point of the previous segment to the last point of this segment as points of that segment. I'll look into it, whether I can merge the first near-empty segment into the second segment. One follow-up question, though, before I dive into that: If you create and individual route with, let's say, five items, the resulting GPX will have five segments. If you delete the first one (single point only) - will then your Garmin cope with the rest (four segments)? Or can it handle single-segment GPX tracks only? |
OK, I tested this. Garmin Connect (the Android app used for connecting to the watches, not the watch itself) will always just see the first track segment and ignore the rest. |
PR #15719 will change c:geo to use only a single track segment on exporting an individual route as track |
Describe your problem!
When exporting a GPX track from c:geo, the code is strange, for example:
I don't understand why there is this strange first track segment with only one point.
One big issue with this is, that Garmin Connect cannot import such GPX files.
Either it only imports the first, quasi empty track segment. Or it bugs completely and does not import at all.
I experimentally removed this first track segment, and now Garmin Connect can import.
(I just got my first Garmin GPS watch, so I am not yet sure if this is the only reason why c:geo exports fail in Connect, but in this one example, the extra track segment definitely was the cause, and it worked after removing that.)
How to reproduce?
See above.
Actual result after these steps?
No response
Expected result after these steps?
No response
Reproducible
Yes
c:geo Version
2024-04-25
System information
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: