BaseCamp doesn't show correct waypoint symbols from Edge

I created two GPX files with waypoints; each waypoint was assigned a different symbol, so that they covered every possible symbol in BaseCamp.
After putting the files on an Edge 800 (one at a time because of the maximum number of waypoints the Edge supports), the device transfers the waypoints to the file Locations.fit; after that, the GPX file was deleted (manually).
As expected the Edge doesn't support all symbols; those it doesn't are replaced by a blue flag, but the supported ones are displayed correctly.
The Locations.fit file cannot be imported manually in BaseCamp, but BaseCamp will read it from the device. However, when doing so BaseCamp mixes up all waypoint symbols; no one is correct! This applies to BaseCamp for the Mac too. I did my tests with BaseCamp 4.0.1, but I guess this isn't solved in 4.0.2 (at least it isn't mentioned in the change log).

0 Former Member over 12 years ago

Thanks for reporting. We will have someone try to repro this here and hopefully there is a somewhat easy fix.

From what you describe, there seems to be a glitch in our cross-platform code that reads FIT.

0 mariomobiel over 12 years ago

I Tryed tis, and it indeed BC ore the Edge replaces waypoint symbols. What i also saw was that the Symbols (Pictures of the buildings) of the standard waypoints in the Edge (Garmin UK, Garmin US and Garmin Taiwan)appear as Black Balls. The same black balls appear on some of the the transferd waypoints. i know the blue flags are normal for waypoint symbols symbols the edge does not support. if made two screenshots of the before and after transfer.

Basecamp 4.0.2
Edge 800 2.40

0 JaVaWa over 12 years ago

It's not the Edge that gets them wrong; when you check your device you will see that the symbols are the same as on your PC before the transfer (except for the symbols that the Edge doesn't support). The problem is in the FIT read routines in BaseCamp.

0 JaVaWa over 12 years ago

I just read in the BaseCamp for Mac section that the problem is caused by the Edge, not by BaseCamp.
The Edge uses a wrong translation for the symbol names to numeric values, but uses the same wrong translation for displaying them on the screen; that's why they look allright on the device, but not in BaseCamp.

Well, we'll just have to wait for a firmware upgrade then...

0 Former Member over 12 years ago

Thanks for letting me know, looks like I can close the case then.

0 JaVaWa over 12 years ago

I was thinking... Are there other devices that use a Locations.fit file, or is the Edge 800 the only one?
In the latter case: solving the problem with a new firmware would result in getting the wrong waypoint symbols on screen when it reads the waypoints from the fit file (created by the old firmware). Wouldn't it be a better idea to keep it the way it is now, and to change the fit reading routine in BaseCamp? The contents of the Locations.fit file is a proprietary extension to the fit specs anyway...

0 Former Member over 11 years ago

Is there a update for the solution?
I have the same problem.