V DIST TO DEST for the course

[Marko]

Dears,

(eTrex SE) could you explain what stays behind the V DIST TO DEST/V DIST TO NEXT data fields, but for the course?
As for the waypoints it is exactly the difference in elevation, I can't get what's mean for the course.
For the course, the V DIST seems almost a half too low.
Anybody noticed this fact?

Kind regards!

FW4.25

[Marko]

Dears,

seems that this data fields refer only for the waypoints.
But on the eTrex SE we have two data fields TO DEST and TO NEXT, what promises this function also for the course.
Maybe the field tests discover a little mole about this issue.

Some reports about this elsewhere for Fenix 5 though,

Kind regards!

[Marko]

Hi again!

Apparently, I have diagnosed a vertical distance (V DIST TO DEST) problem in my eTrex SE.
This refers only to the Garmin Connect app courses; those made directly in the Garmin Explore app work flawlessly!
As I used to make the courses in the Garmin Connect and then transfer them to my Epix watch which synchronize with the Garmin Explore app (and, in subsequent also with eTrex SE), I encountered the problem.
Three is a particular problem with the proper altitude value od those, non-Garmin Explore course pointa, which I unfortunately can not figure out yet

Any hints are welcomed!

[GPSrChive]

The plot thickens !!

[Marko]

I have found the answer!

Proper V DIST TO DEST value lies in the 'User Data Limitations of the eTrex SE and eTrex Solar'.
It claims:
'When sending or creating files for an eTrex® SE or eTrex Solar outdoor handheld, keep in mind the following limitations:
...
50 courses, 200 points per course'.

For your informatorom: it is not a bug, it is a feature!

[GPSrChive]

That information is also available here, at GPSrChive > eTrex SE or eTrex Solar > Specifications and Operation > Files & Folders.

[Marko]

Precisely, new FW updates allow for exceeding the number of points in a course significantly (and far beyond specification).
You ough to know, that now eTrex SE can handle thousands of points in the course (ultracyclists and ultrarunners will appreciate this improvement).
Only vertical elev. data are vague and they are truncated after reaching 200 course points...

[GPSrChive]

Please provide your source for these improvements? I do not see them listed in the Firmware update change logs for either device.

[Marko]

I did not find confirmation source (and in fact, I didn't look for it), but I think that any eTrex SE/Solar user can give it a go and confirm him/herself.
See some of my courses' Stats:

Spoiler

G1UH4610.png

G1UH5616.png

G1UH5304.png

G1UH5328.png

G1UH5454.png

Anyway: bear in mind that some elevation data are missing, which is weird and confusing for me (subject of this topic)...

[Marko]

Precisely, new FW updates allow for exceeding the number of points in a course significantly (and far beyond specification).

Sorry, I must admit that I was wrong!
In fact, given in the specification limit of 200 course points is valid (was not changed by FW 4.25).
The point is, that unfortunately I missunderstood the meaning of track points with the route points (course points).
When uploading the GPX files to the Garmin Explore we have three cases:

GPX track (limit 10) with "unlimited" number of points,

GPX route (limit 10) with limited, 200 course points, and

GPX Waypoints (250).

P.S.
For the matter of further explanation, I am using the small and big capital letters to distinguish the 'course points' in the GPX track (eTrex SE) and the 'Course Points' in the GPX route.

In the Garmin Watch or Edge, Course Points are custom makers you can add to a route using Garmin Connect platform to highlight important locations

.
The eTrex SE is incompatible with the Garmin Connect, though. Nevertheless, everyone still can transfer the course from Garmin Connect to Garmin Explore (and eTrex SE) 'by proxy', using the Garmin Watch or Edge.
From this point of view, eTrex SE is partially compatible with Garmin Watch or Edge (with slight malfunctioning with regard to improper time arrival and somehow fixed, wrong 'V Dist to Next' data).
'All Stats' with given 'Course Points' (GPX route points) and 'Points' (GPX track points) saved and used in the single 'course', see in the picture:

Spoiler

G1V91619.png