Community imports

Saving someone else's route#

Another rider's public route carries Import to Library, which you will see on Explore and on a public page opened inside the app. Press it to keep a copy of a route you like, rather than asking the rider to send you a file.

1. Open the route on Explore, or on a public page inside the app.
2. Press Import to Library.

INVIA puts a copy of the route in your library straight away, so you can open it, file it and ride it without going back to Explore to find it again.

What you see afterwards:

• The copy is in your library, and it is private, so saving a route never shares anything of yours.
• The copy is tagged Imported, which is how you tell it apart from a route you drew.
• The copy is filed under Community Imports in the Home sidebar.

That section exists because a saved route follows different rules from one you made, so INVIA keeps the two apart instead of mixing them in one list. Anything outside Community Imports is yours to export, and anything inside it came from another rider.

What you save is a copy rather than a link to their route. The line, the waypoints, the name, the write-up, the difficulty and surface classifications and the route color are written into your own library the moment you press Import to Library. If the rider later makes their route private or deletes it outright, your copy is untouched and keeps working exactly as before, so nothing you saved depends on them keeping the original.

Provenance#

The copy's item page shows Imported from {rider}, so you can still see whose route it was months later, rather than guessing why it is in your library.

The name in that line comes from the rider's profile, which makes it the only part of the copy that still reads from them. Everything else was written into your library when you saved.

That line stays through editing, because the credit belongs to the route rather than to one version of it.

1. Load the copy into the builder.
2. Edit it.
3. Save it as new.

The new route still shows Imported from {rider}. It is a community import as well, so export is not offered on it either, no matter how much of the line you redraw.

What you can do with it#

A community import behaves like your own routes in every way except the file, so you can:

• View it.
• Rate it.
• Tag it.
• File it into collections.
• Send it to your device.

Sending always works, which means a community import reaches a Garmin the same way your own routes do and you can ride it without exporting anything.

What you cannot do#

You cannot export the GPX of a community import, because the file belongs to the rider who shared it and it is theirs to give away rather than yours.

What you see on the copy:

• GPX is hidden on its card.
• Export GPX is absent on its item page.
• Allow downloads is not offered for it, because you cannot hand out permission over a file that is not yours.

What still works:

• The copy stays in your library, so the export rule takes nothing away from you.
• You can still view, rate, tag and file it.
• You can still send it to your device.

What to do:

• Send the copy to your device instead of exporting it, which gets the route onto a Garmin without a file leaving INVIA.
• Ask the rider who shared the route to switch on Allow downloads on their own route, because that switch is theirs to set and not yours.
• Export rules.

A collection holding a community import#

A collection that holds a community import cannot be downloaded as one file, because that one file would carry another rider's route away inside it.

What you see on that collection:

• GPX is not offered on the collection.

What still works:

• The collection opens as normal, and every route in it still opens.
• Every route in it still sends to your device.
• Your own routes in it still export one at a time.

What to do:

1. Take the community import out of the collection.
2. File the community import in a collection of its own.
3. The first collection now holds only your own routes, so GPX is offered on it again.

Limits#

The allowance counts community saves only, which means it moves when you press Import to Library and at no other time. It does not limit routes you build, import from a file, or record.

A free account that reaches the allowance saves no more routes from other riders, and the copies you already saved stay in your library, so nothing you collected is taken back.

What a refused save looks like:

• A notice reads Community save limit reached and offers Pro for unlimited saves, so the refusal names the limit you reached rather than failing quietly.
• A See Pro plans button sits beside the notice wherever the plan picker is open to you, which puts the upgrade one press from the message.
• The save does not happen, and nothing else on the screen changes, so the route you were looking at is still there and nothing already in your library is touched.
• The larger upgrade panel carries the same limit in its own words, reading You’ve used your free community saves.

What still works:

• Everything already in your library still opens, still draws on the map and still sends to your device, because the allowance decides what you may add rather than what you may keep.
• You can still open any public route or collection page and look at it, so the allowance costs you the save and not the view.
• Sending to a device runs on its own separate free allowance, which means a community save you cannot make takes nothing off your device sends.
• Saving a file copy of a community import is never offered whether you are at the allowance or below it, so the limit takes nothing away there.

What to do:

• To keep saving, upgrade to Pro, because Pro removes the allowance on community saves.