H1 and BaseCamp

[Przekątny]

I have a few questions about the H1's compatibility with Base Camp.

Does data sent from Base Camp go to the correct directory on the device?

For example, the EDGE 520, data sent from Base Camp goes to the correct
location in a file named tempe.gpx.

Does Base Camp display maps from the device?
Does Base Camp receive data from the device?
Does Mapinstall work with the H1?

[JungleJim]

So I tried this, on a Windows PC. Note, I don't use Basecamp that much so I'm not into all the details of what you can do with tracks, routes and waypoints.

When you connect the H1 Basecamp will display a warning that transferring Routes, Tracks and Waypoints is not supported. However, this seems to work fine.

Sending tracks and routes to the H1 works fine. The tracks and routes you select will be placed in a GPX file in GARMIN\NewFiles (I think the name was temp.gpx, but not sure).

Sending waypoints also works, Basecamp will create a waypoints.fit file in GARMIN\NewFiles that is read by the device on startup. Note that the waypoints.fit contains all existing waypoints on the H1 plus the ones selected in Basecamp.
Note that the icon of existing waypoints may get changed. The H1 supports single color or multi color icons for a waypoint. Basecamp seems to overwrite multi colored icons with their corresponding single color one.

Reading of maps on the H1 also works, but is as slow as on the GPSMAP 67.

MapInstall also works, the H1 is recognised and a map gets installed just fine.

Receiving data I did not check yet.

[Przekątny]

Thanks for checking.

I also rarely use Base Camp, but it's useful for some things, and despite the questions asked, I never send anything to the device, not even a map – I simply asked out of curiosity.

I don't know what's going on with the icons.
Icons aren't sent to the device in GPX or Fit files; there's only a tag with icon information. If the device's icon set doesn't include the icon included in the information, the device will use the default icon.

[JungleJim]

After comparing the FIT file on the H1 containing the waypoints (GARMIN\Locations\locations.fit) and the FIT file Basecamp generates (waypoints.fit), it is clear that the Basecamp file does not contain the metadata that specifies whether the icon is single color or multi color, and if it is single color, what color. The basecamp file only contains the id of the symbol, no color information.

That seems to explain why the icon of a waypoint already existing on the H1 reverts back to the default blue color when sending waypoint data from Basecamp to the H1.

[Przekątny]

When it comes to fit files from an external source, I didn't pay attention to the presentation of icons on my device ( Oregon 650T),
I can't tell anything about the gpx file created in Base Camp and copied to the device either, generally I only use one icon in the form of a point.

Now I'll take a closer look at whether there's a difference in the icon presentation between the fit and GPX files.

[Przekątny]

I got a bit carried away with checking the presentation of icons,

I didn't take into account that my device doesn't read routes from the fit file... it reads the file
but when launched directly from the fit file with the "Go" option, it interprets the route as a course (track).

[Przekątny]

That seems to explain why the icon of a waypoint already existing on the H1 reverts back to the default blue color when sending waypoint data from Basecamp to the H1.

I also have a question about waypoints and their icons in the H1.
In older receivers, waypoints (in the saved GPX file "RoutePointExtension") were displayed
as a pin with a blue head. Has anything changed?

I almost forgot about the "pins"; I have their display disabled, which gives me a clear route track at every zoom level, not obscured by pin icons.