Reference

This part is for looking something up, rather than for reading a screen from top to bottom. Come here when something is not working, when you want the keyboard instead of the mouse, or when a link or a control is not where you expected it.

Troubleshooting#

The troubleshooting index lists symptoms in the words a rider would use, so you look up what you are seeing rather than guessing which screen owns the problem. Each entry points at one heading on one page, which means you land on the paragraph that explains the cause and gives you the next step.

Every fix also sits on the page for the screen it belongs to, so you can reach it either way. Come in through the index when you can name the symptom, and read the page for the screen you are on when you want the whole picture around the fix.

Keyboard shortcuts#

INVIA listens for a small set of keys, and this part gathers them into one table so you are not hunting for them across the guide. Most of them belong to the route builder, because that is the screen where your hands are already on the keyboard. Esc steps back out of the tool you are using, and Enter saves an open waypoint editor.

Esc backs out of one tool at a time, so it cancels Detour first, then Trim, then returns Add POI or Explore to Add Point, and then leaves Split. Press it once for each step you want to take back, which means a detour you marked and then dropped costs you nothing but the press. The Edit tools.

The cursor is already in the name box when a waypoint editor opens, so Enter saves the waypoint and closes the editor, and Esc closes it without saving. Nothing you typed is kept when you close it that way, so press Enter or Save when you want the name to stick. Kinds and storage.

The route builder holds the most of these, because undo, redo, removing the selected waypoint and that layered Esc all belong to it. Nearly every other screen listens only for Esc to close what is open. The one screen with a set of its own is the banner editor inside an event, where the arrow keys nudge the selected piece and Delete removes it. Make a banner.

The table names the key, what it does and which screen it works on, so you can tell whether a key applies where you are before you press it.

Appendix: legacy pages#

Links to the older INVIA help site still open. Addresses under /answers/ forward to the page in this guide that now covers the subject, so a bookmark you saved last year still lands on current instructions instead of on a missing page.

The page you arrive at may carry a different name from the one you remember, because this guide is built around the screens of the app rather than around topics. The appendix lists the old addresses beside the pages they now open, so you can confirm you were sent to the right place.

Appendix: not shipped#

This appendix names what the web app does not do, so a control you cannot find is one that does not exist rather than one you have missed. Each entry also says what INVIA does instead, because the way through is more use to you than the gap.

Export is GPX. There is no KML, TCX or FIT export button, and TCX import is refused. Coming in is wider than going out, because INVIA reads GPX, KML and FIT files, and a TCX file you pick is turned away with a note that TCX is still to come. What INVIA imports. Export rules.

Sharing your position as you ride is part of the INVIA app, so on the web you share through a satellite tracker such as a SPOT or an inReach instead. You register the tracker once and its feed is what other riders follow, which means the position comes from the tracker rather than from the browser you are signed in on.

Offline maps on the web means the Garmin map builder, which writes a map onto the device rather than into a browser. The map you build there rides with you on the Garmin, so a ride without signal is covered by the Garmin rather than by a copy of the web map. The map builder.