You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using gexporer+gimporter (on Fenix 7), all waypoints set along a track in a GPX file are shown on "Up Ahead", when navigating, at the same distance as the total track length. Plotting a similar route and adding course points in garmin connect works. Maybe they export the data in a different way, or the distance calculations in gexporter is wrong? See files below.
files.zip
atest.gpx = input file
atest.gexporter.fit = file generated by gexporter
atest.garmin.connect.fit = a similar file generated by garmin connect
I didn’t see any logic in the code that calculates distance for custom course points, even though that would be very useful. It looks like this should be added to the writeFit function. Inside the loop
for (WayPointwpt : trkPoints) {
// …
}
you need to check whether there’s a course point with the same coordinates, and if so assign to it the distance computed up to that moment.
Is this enhancement planned? If you don’t have the capacity to implement it, I could try to add this functionality myself.
Fixed in #38: course points from GPX waypoints now get the distance and timestamp of the nearest track point, so "Up Ahead" shows them at the right place. With your atest.gpx: one/two/three at 1151/2025/3061 m instead of no distance. Thanks for the files!
Activity
kampybs commentedon Aug 23, 2025
I didn’t see any logic in the code that calculates distance for custom course points, even though that would be very useful. It looks like this should be added to the
writeFitfunction. Inside the loopyou need to check whether there’s a course point with the same coordinates, and if so assign to it the distance computed up to that moment.
Is this enhancement planned? If you don’t have the capacity to implement it, I could try to add this functionality myself.
haraldh commentedon Aug 23, 2025
Go ahead and try to implement it correctly. I currently have no capacity right now.
haraldh commentedon Oct 21, 2026
Fixed in #38: course points from GPX waypoints now get the distance and timestamp of the nearest track point, so "Up Ahead" shows them at the right place. With your atest.gpx: one/two/three at 1151/2025/3061 m instead of no distance. Thanks for the files!