Select modes and clean-up

The Collections page gives you two select modes, because tidying up inside one collection and tidying up your whole library are different jobs. One mode ticks the routes inside a single collection, and the other ticks whole collection cards so you can act on several at once. Each mode opens its own action bar with the buttons that make sense for it. Clean up is a separate Pro tool that hunts down duplicate collections for you.

Selecting routes inside a collection#

Use this mode when you want to pull several routes out of one collection, or send them to your Garmin together, rather than opening each route on its own.

1. Expand the collection.
2. Press Select in the open collection header.
3. Tick the member routes you want.

Select is in that header only when the collection holds at least one route, because an empty collection has nothing to tick. The action bar then replaces the open collection header, so the buttons sit where you are already looking.

The four action buttons stay disabled until you tick a route, so a press can never act on nothing. Collapsing the collection leaves select mode and clears your ticks, which means you start the selection again if you close the collection by accident.

Remove#

Remove takes the ticked routes out of this collection without deleting them, so it is the way to move a route elsewhere rather than to get rid of it. It asks Remove N routes from collection? first, and dismissing that prompt keeps the routes where they are.

What you see after you confirm:

• The routes are no longer listed inside this collection.
• Select mode closes.
• INVIA redraws the collection cover without them, so the cover matches what is left.
• A message names where each route went.

What still works:

• The routes are not deleted.
• A route you moved out is on your Routes list, or on your Rides list for a ride.
• That route's own waypoints went with it.
• A route another collection owns stays stowed inside that collection.
• The route stays in every other collection that holds it.
• Waypoints you added to this collection stay in this collection.

The message reads Moved to Routes. Its waypoints went with it. for a route you own, and it names Rides instead when the item is a ride. For a route another collection owns, the message says the route stays stowed inside that collection rather than landing on your Routes list. That message is not a failure, because the route did leave this collection.

Two different failures can stop a removal, and only one of them names a cause. If INVIA removed nothing, it says so and gives the reason, which is that the collection may not be yours. There is no fix to offer for that one, because you can only remove items from a collection you own. If the removal fails outright, INVIA says nothing was changed and then either names the reason or asks you to try again.

Neither failure leaves a route half removed, so the routes are still listed inside the collection, which means a retry is safe and leaving select mode changes nothing.

Selecting collections#

Use this mode to act on whole collections at once, because downloading or sending a season's worth of collections one card at a time is slow.

1. Press Select in the Collections page header.
2. Tick the collection cards you want.

Select is in that header only when you have at least one collection.

This bar has no Share, so sharing a collection means leaving select mode and pressing Share on the card itself, because a card's own buttons come back only when the bar is gone. Route select mode inside an open collection is the exception, because its bar does carry Share.

While select mode is on#

• The visibility pill on each card is inert. Pressing it ticks the card instead.
• The GPX, Share and Send to Device buttons on the cards are hidden.
• Clean up and Select are hidden from the page header.
• Drag to reorder is off.

Every card control gives way to the bar, so a stray press ticks a collection instead of changing one. Everything on that list comes back when you press Cancel, because nothing about the collections themselves changed while the bar was open.

GPX on collections#

A collection holding a route saved from another rider cannot be downloaded as a file. Ticking one alongside the rest does not stop the batch, because INVIA downloads what it can and then tells you about the rest.

What you see when you tick one of those:

• The download runs for the collections that are allowed.
• A message states how many collections were skipped and why.
• Those skipped collections are still on the Collections page.

If no ticked collection is allowed, INVIA writes no file. The message tells you to send to the device instead, which is how those collections still reach your Garmin, because Device in the same bar is not subject to that block. The same wording appears on a single locked route, where the download is locked and INVIA points you at the device instead.

Device on collections#

INVIA writes each ticked collection to the Garmin as one GPX file, so each collection lands on the Garmin as its own file rather than as one merged pile. The storage and arrows dialog appears once and INVIA reuses that choice for the rest of the batch, so you answer it once for the whole send.

If the Garmin is not connected, INVIA queues the first collection of the batch and stops there, then opens the Device page and tells you it is waiting for your Garmin. Nothing is written to the Garmin.

Only that one collection is queued, because the send needs a connected Garmin and the batch cannot go on without one. Everything else you ticked is not queued at all, so once the first collection has gone to the Garmin you tick the rest again and send them.

A bar at the top of the Device page names the queued collection and repeats the wait. Plug the Garmin in and INVIA asks once whether to send it now, with Send and Not now. Pressing Not now leaves the collection queued on that bar, and the bar carries a Send now button as soon as the Garmin is connected, so you can start the send yourself. The X on that bar cancels the queued send outright.

If you dismiss the dialog, the batch stops there. The collections already written stay on the Garmin, and the rest are untouched and still on the Collections page, so tick them again to finish the job.

Delete#

Delete removes the collections and keeps their routes, which is why the confirmation reads Delete N collections? and Routes will be moved to My Routes. This can't be undone.

What you see after you confirm:

• The ticked collections are no longer on the Collections page.
• Select mode closes.
• INVIA confirms each one with Collection deleted.

What still works:

• The routes from the deleted collections are in My Routes.
• Each deleted collection's own pins are in your waypoint library, labelled with that collection's name.

Delete dissolves the container and nothing else, because the routes inside are never deleted with it. Their folder label is reset to My Routes, which is where the picker titled Add routes to "{name}" finds them again.

The collections themselves are deleted and that cannot be undone, so getting one back means making a new collection and adding its routes to it again from My Routes.

If a delete fails, INVIA says nothing was changed and asks you to try again. That collection is still on the Collections page with its routes inside, so nothing is lost while you retry and no collection is ever left half deleted.

Clean up (Pro)#

Clean up is in the Collections page header, and it appears when you have more than one collection. It finds duplicate collections and removes the extras, so a library that filled up with repeats gets tidied without you comparing cards yourself. It is a Pro feature.

Two collections are duplicates when either line is true:

• They have the same name, ignoring capitals and outer spaces.
• They hold the exact same set of routes.

An empty collection never matches by routes, so blank collections are grouped only by their name. Matches carry across a group, which means that if A matches B by name, and B matches C by routes, all three land in one group.

The panel is titled Clean up collections, and each group heading states how many collections are in it and whether they matched by name or by routes. Each row shows the collection name, its route count and its creation date, so you can tell the copies apart before anything is removed.

INVIA picks one collection in each group to keep, taking the one with the most routes and breaking a tie by keeping the oldest, so the fullest copy survives. That row is marked KEEP, and every other row is marked REMOVE and ticked for you.

Change that choice by ticking or unticking a row. One collection in each group always survives. INVIA refuses a tick that would mark every row in a group, so a group can never be emptied out.

The footer counts what is marked and states that routes stay in My Routes, so you can check the number before you commit to it. Press Remove N collections to go on.

The confirmation reads Remove N collections? and The collections you marked will be deleted. Their routes are kept and moved back to My Routes. This can't be undone.

What you see after you confirm:

• The removed collections are no longer on the Collections page.
• The kept collection in each group is still there, with its routes inside.
• The routes from the removed collections are in My Routes.
• The panel stays open and recounts the groups.

Clean up never deletes a route, so what you give up is the spare collection and never anything inside it.

When no duplicates remain, the panel says no duplicate collections were found. It states that it compares by name and by the routes inside, so you know what it looked at. You see the same message when you open Clean up on a library that never had duplicates, and closing the panel leaves your collections unchanged.

The library and waypoint clean-up tools are described under Duplicates and bulk import.