How waypoints travel
What happens to waypoints when a route is saved, filed into a collection, downloaded as GPX, or sent to a Garmin: the package set, the 50 meter fold, the 500 waypoint soft cap, and device import.
Last checked against the live app on 3 September 2026.
Waypoints travel with whatever carries them. A route carries its own, and a collection carries every member's waypoints plus pins of its own, so you never send places separately.
With a saved route#
Waypoints always travel with a saved route, which means nothing you marked on the line is left behind when you save. Each route carries its own copy of its named waypoints and pins, so the route arrives complete wherever you send it.
With a collection#
A collection carries every member's waypoints plus pins of its own, and INVIA builds one package set from all of them so the collection travels as one thing rather than as separate lists.
The same place often sits in more than one member, because consecutive stages meet where you stop. INVIA folds those copies into one entry when they are within 50 meters of each other.
What the fold does for you:
- A fuel stop shared by two consecutive stages lands once, not twice, so you are not scrolling past the same stop on the device.
- Each member keeps its own copy in your INVIA library, because the fold applies to the package being sent rather than to what you have saved.
- No waypoint is removed from your waypoint library.
In a GPX download#
Waypoints go into the file as standard waypoint entries with name and description, which is what other mapping apps and devices expect to read.
| Download | What the file holds |
|---|---|
| A route | The line and that route's waypoints. |
| A ride | The line and that ride's waypoints. |
| A collection | Every member's line and the whole package set. |
On a Garmin: one route#
A single route's waypoints go as saved places alongside the track rather than as a route of via-points, so no stray gray line connects them on the map.
Before a single-route send, INVIA offers any saved waypoints within 750 meters of the line, because a place you marked that close is usually a place you want on the ride. The prompt reads N saved waypoints near this route. Include them with this route on the device?
- Press Include N to send those waypoints with the route.
- Or press Skip to send the route on its own.
Press Skip and those waypoints stay in your INVIA library. The route reaches the Garmin either way, and so do the route's own named waypoints. Skipping leaves out only the nearby extras, which you can send later from your waypoint library.
On a Garmin: a collection#
A collection sends as two files, and the pair counts as one device send, so a twelve-stage trip does not spend twelve sends.
| File | What it holds |
|---|---|
| One multi-track file | The line of every member. |
| One saved-places file, named after the package | Every waypoint in the package set, de-duplicated across the package. |
A collection send never offers the nearby waypoints prompt, because that prompt belongs to single-route sends from the builder, from a route's page and from the route drawer. Send a collection and INVIA goes straight to these two files, so a saved waypoint lying near the line that you have not attached to anything does not travel with the package. Attach it to a route or to the collection first if you want it on the Garmin.
The saved-places file has a soft limit of 500 waypoints. Above that limit some waypoints are left off, so the send finishes rather than failing outright.
INVIA lines the package's places up route by route, in the order the routes are sent, with the collection's own pins last. The first 500 travel and everything after that point is left off, so the places at the end of the order stay behind rather than a pick of the least useful ones. The collection's own pins sit at the end of that order, which means they are the first to fall off.
What you see and what to do:
- INVIA shows a warning that counts what was left off and names the first three of them, so you know how many places did not travel.
- The multi-track file is on the Garmin, and so are the saved places that fit within the limit.
- Every waypoint left off is still in your INVIA library.
- Read the warning for the count and those first names, then send the rest from your waypoint library with Send this group to device.
From a Garmin, and back#
On the Device page, the Waypoints panel lists the device's saved places by source file, because that is how the Garmin stores them.
- Press Import all to save every device waypoint to your library.
- Or select some waypoints and import only the selection.
A waypoint already in your library within 15 meters is skipped, so importing the same Garmin twice does not fill your library with copies of one place.
What a skip means:
- The saved count is lower than the number of waypoints on the device.
- The waypoint already in your library is left as it is, so nothing you have saved is overwritten.
- The waypoint on the device is left as it is.
- Do nothing about a skip, because re-importing never creates duplicates.
Deleting a waypoint on the device#
Garmin stores waypoints inside files rather than one at a time, so deleting one waypoint from the device removes the whole file it sits in. The delete is Pro.
On a Free account the control is still there, drawn as a padlock in place of the bin. Pressing the padlock says Managing files on the device is a Pro feature, offers the plans and touches nothing on the Garmin. Everything else on the panel is unchanged, so a Free account can open the file groups, read their waypoint lists and press Import all to bring every device waypoint into the library.
After the delete:
- The file's group is gone from the Waypoints panel. Every waypoint that file held is gone from the device.
- Your INVIA waypoint library is unchanged. Every waypoint you imported is still there.
- Import the waypoints before you delete the file, because the delete cannot be undone.