Workaround for erratic Courses

[Andy]

I think this is another GPSMAP67 bug regarding Courses, but I couldn't find any other report of this so I assume it might be happening only in my device.
I often get erratic behavior when selecting a Course through the main menu, whether this is a course created in Basecamp or a downloaded track that I have converted to a Course in the GPSMAP67.
There are no problems with courses that I create in the device, by choosing each waypoint in the device itself.

Previously I'd manage to get the correct route by selecting "direct route" instead of "roads and trails", but I wouldn't have any turn warnings.
Fortunately a discussion regarding bug n.35 helped me find a workaround for this bug too, so thank you for that.

If I select a course from the "course planner" in the main menu, and then select "roads and trails" navigation, the GPSMAP immediately starts a calculation and once finished and I hit GO, it starts calculating once again. Once it has finished the second round of calculations the route suggested and also the destination are totally different from the original. In one case a round trip became a one way route to a completely different area.

If however I select the same course in the FIND menu by pressing the Find button, there is only one route calculation and that's after hitting GO.
The subsequent route is as expected: it corresponds to the original, and I get turn warnings.

[GPSrChive]

Firmware version, please.

[Przekątny]

I often get erratic behavior when selecting a Course through the main menu, whether this is a course created in Basecamp or a downloaded track that I have converted to a Course in the GPSMAP67.
There are no problems with courses that I create in the device, by choosing each waypoint in the device itself.

I assume that in Base Camp you are planning a route (course) on a different map than you have on your device.

In order for the route (course) created in Base Camp on your device to run as expected, the route (course) should be marked out on the same version of the map that we will be using on the device.

Carry out a test to mark a route (course) in Base Camp after connecting the device and indicating the map that you have on your device.

For the test, you can copy the map from the device to the SD card and read it in Base Camp using a reader, the map file should be copied to the Garmin directory on the SD card.

[javawa]

BaseCamp cannot create courses, only routes, tracks and waypoints. Routes and courses are different beasts, naming courses as synonymous with routes is confusing. You can convert a route to a course in the device, just as converting tracks to courses.
I've got the impression that the conversion routines for courses in outdoor devices still haven't reached maturity. Those built in Edge devices are much, much better.

[JungleJim]

I think this is another GPSMAP67 bug regarding Courses, but I couldn't find any other report of this so I assume it might be happening only in my device.
I often get erratic behavior when selecting a Course through the main menu, whether this is a course created in Basecamp or a downloaded track that I have converted to a Course in the GPSMAP67.
There are no problems with courses that I create in the device, by choosing each waypoint in the device itself.

Previously I'd manage to get the correct route by selecting "direct route" instead of "roads and trails", but I wouldn't have any turn warnings.
Fortunately a discussion regarding bug n.35 helped me find a workaround for this bug too, so thank you for that.

If I select a course from the "course planner" in the main menu, and then select "roads and trails" navigation, the GPSMAP immediately starts a calculation and once finished and I hit GO, it starts calculating once again. Once it has finished the second round of calculations the route suggested and also the destination are totally different from the original. In one case a round trip became a one way route to a completely different area.

If however I select the same course in the FIND menu by pressing the Find button, there is only one route calculation and that's after hitting GO.
The subsequent route is as expected: it corresponds to the original, and I get turn warnings.

This is indeed the bug (nr 35) that a different course that’s on the device is loaded than the one you actually selected in the Course Manager, depending on your course navigation settings.

Using Find will load the correct one. Another workaround is to start navigation of a course from the Explore app, and not from the device itself. That will load the correct course.

I suggest you report it to Garmin support. They should have a case for it so be sure to get added to that one. It may take support some convincing though. You can point them to this Garmin forum post as well. Garmin support contacted me based on that topic.

[JungleJim]

I assume that in Base Camp you are planning a route (course) on a different map than you have on your device.

In order for the route (course) created in Base Camp on your device to run as expected, the route (course) should be marked out on the same version of the map that we will be using on the device.

Carry out a test to mark a route (course) in Base Camp after connecting the device and indicating the map that you have on your device.

For the test, you can copy the map from the device to the SD card and read it in Base Camp using a reader, the map file should be copied to the Garmin directory on the SD card.

The issue Andy mentions is not related to differences in maps on the device and the one used during planning. The issue is that the unit loads a different course from the device than the one you actually selected.

Besides, as javawa also mentioned, you cannot plan courses in Basecamp, only routes or tracks.

[Przekątny]

BaseCamp cannot create courses, only routes, tracks and waypoints.

I didn't want to draw attention to the fact that Base Camp doesn't create courses, so I used the term route and in brackets (after processing) course.

Devices have different route calculation algorithms, different from Base Camp as well, Garmin introduced "rigid" route calculation in Base Camp, which makes the route in the device consistent with the route that was planned in Base Camp, provided that the same map versions are used in Base Camp and in the device.

In my opinion, the course in the device is always designated as a route according to the device algorithm using the "roads and trails" option.

In this case, you should use navigation with a saved route

[Przekątny]

This is indeed the bug (nr 35) that a different course that’s on the device is loaded than the one you actually selected in the Course Manager, depending on your course navigation settings.

In my opinion, this is a wrong interpretation, it is about the same course, determined on the basis of the selected activity algorithm and device.

[JungleJim]

In my opinion, this is a wrong interpretation, it is about the same course, determined on the basis of the selected activity algorithm and device.

I’ve done extensive testing on this issue and it is simply a case of a different course being loaded. It is very clear because instead of the course you selected, the exact path of a different course is displayed by device.

So it’s not a matter of deviations in the path due to map differences, but an actual different course being loaded.

If you have a GPSMAP 67 you can try reproducing it yourself.

[Przekątny]

So it’s not a matter of deviations in the path due to map differences, but an actual different course being loaded.

In the case of a consistent route in the device and Base Camp, the same version of the map is required, not limited to the visual course of the roads but takes into account the coordinates of the nodes and the difference in the categorization of the roads.

I do not take into account minor deviations from the expected route, the difference can be significant, there can be a completely different course of activity hiking and cycling (road) from the same course. Reaching the destination for a pedestrian may be from the east and for a cyclist from the west, on the same map and from the same file due to the lack of a (short) section of the road intended for cyclists or incorrect categorization and according to our knowledge, a bicycle can travel the same route that a pedestrian travels.
The device works according to the assumed parameters, searches for e.g. the shortest access although according to the user this is not the appropriate route designation.