From 39454f0b839191b7829a33ebed336a0f521bf4e2 Mon Sep 17 00:00:00 2001 From: vcoppe Date: Wed, 28 Oct 2026 18:22:00 +0100 Subject: [PATCH] update docs --- website/src/lib/docs/en/gpx.mdx | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/website/src/lib/docs/en/gpx.mdx b/website/src/lib/docs/en/gpx.mdx index 89707ab92..866b80123 100644 --- a/website/src/lib/docs/en/gpx.mdx +++ b/website/src/lib/docs/en/gpx.mdx @@ -3,6 +3,7 @@ title: GPX file format --- @@ -30,8 +31,17 @@ However, the hierarchy described above allows for more advanced use cases, such ### Routes -A **route** is a single continuous path described by a sequence of **route points**, which are the places to go through, like the anchor points of the [routing tool](./toolbar/routing). -Like a track, it can have a **name**, a **description**, and **appearance properties**. +A **route** is a single continuous path made of a sequence of **route points**. +These are mandatory checkpoints, which correspond to the anchor points of the [routing tool](./toolbar/routing). +The points in between are only a suggested path connecting the route points. +Like a track, a route can have a **name**, a **description**, and **appearance properties**. + + + +Nowadays, most apps and GPS devices work perfectly well with tracks, even for navigation. +However, some of them only work with routes: in that case, you can [convert](./menu/edit) your tracks to routes, or [create](./menu/file) a route file from the start. + + ### Points of interest