Waypoints

A waypoint is a named place you want to find again, a fuel stop, a camp, a gate, a hazard or a view. INVIA attaches each one to the route, ride or collection that needs it, so a waypoint travels wherever that thing goes. Saving it once is enough to put it in your library, on a shared link, in a GPX file and on a Garmin.

The three kinds of point on a route#

A click in the route builder makes one of three different things, and telling them apart saves you hunting for a waypoint that was never one.

Route points never leave the builder, so no route point appears in the Waypoints list, in a GPX file, or on a Garmin, though the line those clicks shape is exported in full. A waypoint takes one of seven types, Fuel, Camp, Vista, Hazard, Food, Service or Custom, and each type draws its own marker so you can read the map without opening anything.

Off route (marker only, don't reroute to it) is checked by default, so most places you drop become pins and your line stays as you drew it. Uncheck the box when you want the route to run to the place, and INVIA inserts the stop into the nearest segment.

Detach turns a stop into a pin, and Detour and Trim do the same to named waypoints inside the section they replace, because that stop no longer has a line running through it. Nothing is deleted by any of the three, so look in the Pins list under the name you gave it. To make a pin a stop again, drop the place once more with Off route (marker only, don't reroute to it) unchecked. The builder tools.

The copy each route keeps#

Each route and each ride carries its own copy of its waypoints, stored as a snapshot separate from the line, which is why renaming one on a route changes that route alone. Every other route keeps the old name, both routes still work and neither name is lost. Use rename-everywhere in the waypoint library when you want the new name on all of them.

Press the X beside a waypoint on a route's page and INVIA asks Remove this waypoint? and states It'll be taken off this route only. before doing anything. Confirm and the Waypoints (N) count drops by one on that route. The waypoint stays on your other routes and in your collections, so open one of those to see it still listed there, and press + Add to put it back on this route.

The Waypoints (N) section on a route or ride lists Start, Finish and every named stop, and owners get + Add with two ways to place one.

If you have saved nothing within 1.5 kilometers, the page reads No saved waypoints near this route. and leaves the route and its existing waypoints alone, so use Drop on map instead. Kinds and storage.

The waypoint map#

Open it from the Home tab under Waypoints, then Open waypoint map. Two pills at the top switch views, because you sometimes want to know what one route carries and sometimes want every pin you own on a single map.

In By container, each section heading counts its containers and each row counts the waypoints it holds, so an empty section reads No waypoints here rather than leaving you guessing. Press the pencil on a row to rename a waypoint in that container only, or press its in N chip to rename it in all N containers, which reports how many containers changed. A rename deletes nothing and moves nothing, so the waypoint stays in every container it was in and keeps its position on the map.

Unfiled holds the waypoints no route, ride or collection carries, and each row offers Rename, File into a collection and Delete permanently so a loose pin either gets a home or leaves your library. Filing moves the waypoint under that collection in the Collections section and out of Unfiled, while Delete permanently asks you to confirm and then names the waypoint it deleted. No route, ride or collection loses anything to that delete, because an unfiled waypoint is in none of them.

If INVIA cannot work out which waypoints are unfiled, it says so and disables the buttons, because a waypoint that a container holds must never be mistaken for a loose one. Press Retry to scan again.

The Library view#

Library puts a map beside a list so you can see every waypoint that has coordinates while you work through it. Group the list by Route, by Collection or by File, and the waypoints on no route sort into buckets of their own.

Region pills narrow the list to one region, and pressing a group heading opens it and zooms the map to it. Each waypoint row carries Add to collection, Add to route, Rename and Delete. Each group heading does the same for the whole group and adds one more button. Send this group to device is disabled until a Garmin is connected, so connect one on the Device tab before you reach for it.

Select ticks waypoints or whole groups, then Send to device or Delete acts on everything ticked, and Cancel clears your ticks and changes nothing. A bulk delete asks you to confirm first and removes the ticked waypoints from your waypoint library, and a delete that fails says so and reloads the real list.

What deleting touches#

Deleting a waypoint from the waypoint library also deletes it from your routes and rides. It does not delete it from collections. That is deliberate, so a collection holds its copy of the place for good, which means a pin you filed into a trip survives any later clear-out of your library. Every collection that held it still holds it and still lists it in the By container view. Dissolve that collection and the copy is put back into your library rather than being lost with it, so filing a place into a collection is never the last you see of it.

Taking a place out of one collection is a separate action from a library delete, so Remove from this collection sits on the pin's own row in the collection's tree. That button acts on the pins the collection itself holds, and it leaves the waypoint in your library. In the Library view the same job falls to a different control, because there you group the list by Collection and the row carries an X labelled with that collection's name. A pin filed into Baja Loop reads Remove from "Baja Loop", and pressing it takes the pin out of that one collection.

Deleting a route or ride copies its named waypoints into every collection that holds that route, and INVIA copies before it deletes, so no named waypoint is lost with the route. The route leaves its list and its waypoints appear under each collection that held it. If the copy step fails, INVIA deletes nothing and the route is still there.

Clean up, a Pro tool#

Clean up sits in the waypoint library header and opens three tabs, Duplicates, Orphans and Files, each carrying a count so you can see how much there is to do before you start. It works only on your own data and shows what it will keep and what it will remove before you press anything, though what it removes is irreversible once you confirm.

Names carrying a different number or direction never merge, such as Camp 1 and Camp 2, Upper and Lower, because those are two places rather than two copies of one. Merging keeps the most-attached waypoint, moves the other copies' route, ride and collection attachments onto it, and deletes the extras only after those moves succeed. If any step fails, INVIA deletes nothing. What you get is one waypoint for that place in your library, held by every route, ride and collection that held a copy, plus a message counting what was merged. Not the same marks a group as two different places and INVIA never offers that pair again, which deletes nothing and merges nothing.

Orphans are waypoints attached to nothing, and each row names the nearest route or ride within 2 kilometers so you can decide where it belongs. Press Attach to put the waypoint on that route or ride, which takes the row off the list and drops the tab count by one. Tick and delete instead when a pin has no use, and nothing else loses anything, because an orphan was attached to nothing. If INVIA cannot verify the attachments completely it refuses to offer deletion and draws no delete button, so close the panel and open Clean up again to retry.

The Files tab lists the source-file labels your waypoints arrived with, so you can rename a label, merge one label into another, or give a label to waypoints that have none. Labels are the only thing that tab changes, which means no waypoint is deleted and no attachment moves. Waypoint library and clean-up. The clean-up tools for duplicate routes and duplicate collections live under Duplicates and bulk import.

Into a GPX file#

A route carries its own waypoints and a collection carries every member's waypoints plus pins of its own, which INVIA builds into one package set before it writes a file. The same place sitting in two members folds into one entry when the copies are within 50 meters, so a fuel stop shared by two consecutive stages lands once, not twice. Each member keeps its own copy in your library, because the fold changes the file rather than your data. Collections.

Onto a Garmin#

A single route's waypoints reach a Garmin as saved places alongside the track rather than as a route of via-points, so no stray gray line joins them on the map. Before that send INVIA offers any saved waypoints within 750 meters of the line, reading N saved waypoints near this route. Include them with this route on the device? Press Include N to send those along, or Skip to send the route on its own. The waypoints you skipped stay in your INVIA library, ready to send later.

A collection sends as two files, one holding a track per member and one holding every waypoint in the package set, and the pair counts as one device send. The saved-places file has a soft limit of 500 waypoints, so above that some are left off rather than the whole send failing.

The multi-track file and the saved places that fit are already on the Garmin by the time you see any warning. INVIA writes both files, then reports that the send succeeded and counts the waypoints it wrote, and only after that shows a second, separate message counting what was left off. That warning names the first three of them, so the send finished and the warning is about the places that did not fit rather than about a send that failed. Nothing is lost to the limit, because every waypoint left off is still in your INVIA library. Read the warning for the names, then send those from the waypoint library with Send this group to device. Sending.

Back from a Garmin#

The Device page's Waypoints panel lists the Garmin's saved places by the file each one came from, so press Import all for a whole file or select some and import only the selection. A place already in your library within 15 meters is skipped rather than saved a second time, which is why the saved count is lower than the number of waypoints on the device. Both copies are left as they are, so do nothing about a skip, because re-importing never creates duplicates.

Garmin stores waypoints inside files rather than one at a time, so deleting one waypoint on the device removes the whole file it sits in and every waypoint that file held. The file's group leaves the Waypoints panel, while your INVIA waypoint library is unchanged and every waypoint you imported is still there. Deleting on the device is a Pro action and cannot be undone, so import a file's waypoints before you remove it. How waypoints travel. Waypoints on the device.

1. 1
   Kinds and storage

   Route points, named waypoints and pins in the builder, what each one is for, how a waypoint is stored as a snapshot on each route, and the Waypoints section of the item page.

2. 2
   Waypoint library and clean-up

   The waypoint map's two views, By container and Library, filing loose pins, rename everywhere, what deleting a waypoint touches, and the Pro clean-up for duplicates, orphans and files.

3. 3
   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.