Basecamp
In Basecamp if you add waypoints for Info Controls with proximity alarms then export to GPX.
That format will alert on Etrex style GPS
It won’t alert on Garmin Edge or Wahoo
Garmin Connect
In Garmin Connect if you add course points for infos to a course. Note descriptions limited to 15 chars as per original 2003-4 TCX / CRS XML spec.
That format when synced will alert on Garmin Edge
If you export to GPX and reimport as a different course it remembers the course points
RWGPS
In RideWithGPS premium if you add custom cues for info to a route. Descriptions not limited to 15 chars
The custom cues will alert on a Wahoo after they pin the route and sync.
I tend to use CTRL / CKPT / INFO <Name> as the description truncating as best I can to 15 chars for Garmin Etrex and Edge.
Organiser Workflow
As to organiser workflow. Basecamp just crashes on my PC these days and I no longer use it.
1. I create course in Garmin Connect, adding course points
2. I export that to GPX, which converts course points to waypoints with additional information Connect recognises should you reimport to a duplicate course.
3. I run it through my simple-gpx utility which adds the additional information for both proximity alarms and Wahoo cue points.
4. The resulting GPX becomes what I offer for Etrex users
5. The resulting GPX is imported to RideWithGPS and it converts the waypoints to custom cues even in basic RWGPS. These can be synced to Wahoo and will alert.
The work on getting it to work with Wahoo devices was done with Diesel’s help as he has two such devices to test the results on.
But
However…
1. With increased entries for PBP this year, I used some of the entry fees to pay for a premium RWGPS account. I now have RWGPS auto trace the route to also add cues for turn by turn navigation on Wahoo devices.
2. The version of simple-gpx that converts waypoints such that RWGPS recognises then as custom cues on import; only exists on my PC. I never released the updated version for general use on the web.
3. I started work on a more advanced version of simple gpx after Basecamp stopped working on my PC. To do all the manipulation that I used to do there such as splitting and joining tracks, reversing them, changing the start point etc as well as all the existing features of simple-gpx. The new version includes mapping to do some of the work visually with a mouse.
Priorities
But other priorities have taken over at the moment. I likely won’t revisit the next generation of simple gpx till we hit autumn. Thus the new feature for Wahoo custom cue generation remains just for my use for now. Oh and this new version also auto creates a tcx from the gpx as well, as thst was trivial to add whilst in the code.
Important
Note it is important that the latitude and longitude of the waypoints exactly match that of a point on the track in the GPX. My simple-gpx (on PC) finds the nearest track point for each waypoint and makes the coordinates exactly the same. If they are not the same they won’t be recognised as custom cues when imported to RWGPS and won’t alert on Wahoo units.
If it sounds complicated that’s because it is, to get alerts on all of these different types of devices, without duplicating your effort. Hence why I updated simple gpx to do the heavy lifting for me. It took several tests over last winter, with Richard’s help, to get the Wahoo bit working. The main issue being there isn’t a simple document you can read to work out what each device type needs for them to alert your control locations.
If you’d like me to run some gpx (with waypoints) through the version of simple-gpx on my PC and fire them back for you to import to RWGPS basic as custom cues. Then I can do that. But not till next week at earliest.
Remind me next week and I’ll also post here what the waypoints and rest of GPX file needs to look like, for RWGPS to import as custom cues for Wahoo. You can then at least do some manual edits for that, should you wish.
