Migration to new Rust-based engine (#401)

* wasm first steps * parsing start * parsing continued * progress * progress * progress * progress * progress * progress * progress * progress * fixes * reorganize * change type * fix * progress * refactoring * progress * progress * progress * keep style info * progress * progress * remove (copy) in name * progress * merge methods into 1 * splice * progress * progress * progress * cleaning * progress * progress * progress * visibility * progress * progress * progress * progress * progress * fixes * progress * fix markers * fix * progress * progress * progress * progress * progress * progress * small fix * use engine info * fix popups * small fix * progress * progress * progress * clean tool * handle self closing elements * reduce data exchanges across boundary * copy on wasm side to avoid any data corruption * speed fix * routing * refactoring * reverse * reverse * crop * split * merge * progress * time tool * fix bounds for waypoints * reduce * fix reactivity * handle corrupt time data * export * progress * remove gpx js package * remove todo * update readme * cleaning * progress * fix link fields * remove unused fields * refactoring and tests * import and export of routes, ref #192 * per-chunk categories storage * cross-tab sync * outdated state * refactoring * reorder methods * refactoring * fix * improve flow * renaming * progress * progress * fix * progress * per file history * keep original flag * use history variant * fix * progress * file explorer * progress * fix * sticky folders * improved sticky folders * fix sortable * fix sortable * fix * fix tab size * no file delete on desktop * fix routing on other file * fix sorting * remember language * open links in browser * commit missing changes * avoid selecting on resize * clarify filename * explorer actions * fix folder styling * drop anywhere in folder * cleaning * fixes * remove focus-ring * full screen * small fix * consistent highlight color * improved preview * performance improvements * sparser data transfers * sparser data transfers * show popup once data is loaded * fix routing control size * fix * sparse desktop build * remove custom ign styles * use new endpoint for openhikingmap * strip native menu * reorder context menu items * route full support * route - track conversion * create route file action * route export, filter out anchors at high zoom level * clarify name handling * move hide & center to view * routes continued * update docs * fix power format, closes #378 * lint fixes * fix display of additional data with gaps, closes #361 * fix linting issues * fix import modules * fix multidrag * change base to resolve * fix type errors * fix layer typings * fix last type error * each keys * improve typings * deploy to cloudflare --------- Co-authored-by: vcoppe <vcoppe@hexaly.com>
2026-11-01 20:19:39 +00:00 · 2026-10-31 18:08:22 +01:00
1 parent 6a0d434371
commit 8fe7d8d64d
@@ -7,11 +7,11 @@ title: Files and statistics
    import DocsNote from '$lib/components/docs/DocsNote.svelte';
    import ElevationProfile from '$lib/components/elevation-profile/ElevationProfile.svelte';
    import GPXStatistics from '$lib/components/GPXStatistics.svelte';
-    import { exampleGPXFile } from '$lib/assets/example';
+    import { exampleStatistics } from '$lib/data/example';
    import { writable } from 'svelte/store';

-    let gpxStatistics = writable(exampleGPXFile.getStatistics());
-    let slicedGPXStatistics = writable(undefined);
+    let statistics = writable(exampleStatistics);
+    let slicedStatistics = writable(undefined);
    let hoveredPoint = writable(null);
    let additionalDatasets = writable(['speed', 'atemp']);
    let elevationFill = writable(undefined);
@@ -51,7 +51,7 @@ By right-clicking on a file tab, you can access the same actions as in the [edit

 As mentioned in the [view options section](./menu/view), you can switch to a tree layout for the files list.
 This layout is ideal for managing a large number of open files, as it organizes them into a vertical list on the right side of the map.
-In addition, the file tree view enables you to inspect the [tracks, segments, and points of interest](./gpx) contained inside the files through collapsible sections.
+In addition, the file tree view enables you to inspect the [tracks, segments, routes, and points of interest](./gpx) contained inside the files through collapsible sections.

 You can also apply [edit actions](./menu/edit) and [tools](./toolbar) to internal file items.
 Furthermore, you can drag and drop the inner items to reorder them, or move them in the hierarchy or even to another file.
@@ -83,8 +83,8 @@ You can also use the mouse wheel to zoom in and out on the elevation profile, an

 <div class="h-48 w-full">
    <ElevationProfile
-        {gpxStatistics}
-        {slicedGPXStatistics}
+        {statistics}
+        {slicedStatistics}
        {hoveredPoint}
        {additionalDatasets}
        {elevationFill}
@@ -92,8 +92,8 @@ You can also use the mouse wheel to zoom in and out on the elevation profile, an
 </div>
 <div class="flex flex-col items-center w-full">
    <GPXStatistics
-        {gpxStatistics}
-        {slicedGPXStatistics}
+        {statistics}
+        {slicedStatistics}
        orientation={'horizontal'}
    />
 </div>
@@ -3,13 +3,15 @@ title: GPX file format
 ---

 <script>
-    import { Waypoints, MapPin } from '@lucide/svelte';
+    import DocsNote from '$lib/components/docs/DocsNote.svelte';
+    import { Waypoints, Route, MapPin } from '@lucide/svelte';
 </script>

 # { title }

 The <a href="https://www.topografix.com/gpx.asp" target="_blank">GPX file format</a> is an open standard for exchanging GPS data between applications and GPS devices.
 It essentially consists of a series of GPS points encoding one or multiple GPS traces, and, optionally, some points of interest.
+These traces can be stored either as tracks or as routes.

 GPX files may also contain metadata, of which the **name** and **description** fields are the most useful for users.

@@ -27,6 +29,20 @@ Some devices also store additional information such as heart rate, cadence, temp
 In most cases, GPX files contain a single track with a single segment.
 However, the hierarchy described above allows for more advanced use cases, such as planning multi-day trips with several variants for each day.

+### <Route size="16" class="inline-block" style="margin-bottom: 2px" /> Routes
+
+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**.
+
+<DocsNote>
+
+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.
+
+</DocsNote>
+
 ### <MapPin size="16" class="inline-block" style="margin-bottom: 2px" /> Points of interest

 **Points of interest** (technically called *waypoints*) represent locations of interest to show either on a GPS device or on a digital map.
@@ -3,14 +3,14 @@ title: Edit actions
 ---

 <script lang="ts">
-    import { Undo2, Redo2, Info, PaintBucket, EyeOff, FileStack, ClipboardCopy, Scissors, ClipboardPaste, Trash2, Maximize, Plus } from '@lucide/svelte';
+    import { Undo2, Redo2, Info, PaintBucket, ArrowRightLeft, FileStack, ClipboardCopy, Scissors, ClipboardPaste, Trash2, Plus } from '@lucide/svelte';
    import DocsNote from '$lib/components/docs/DocsNote.svelte';
 </script>

 # { title }

 Unlike the file actions, the edit actions can potentially modify the content of the currently selected files.
-Moreover, when the tree layout of the files list is enabled (see [Files and statistics](../files-and-stats)), they can also be applied to [tracks, segments, and points of interest](../gpx).
+Moreover, when the tree layout of the files list is enabled (see [Files and statistics](../files-and-stats)), they can also be applied to [tracks, segments, routes, and points of interest](../gpx).
 Therefore, we will refer to the elements that can be modified by these actions as *file items*.
 Note that except for the undo and redo actions, the edit actions are also accessible through the context menu (right-click) of the file items.

@@ -27,10 +27,6 @@ Open the information dialog of the currently selected file item, where you can s

 Open the appearance dialog, where you can change the color, opacity, and width of the selected file items on the map.

-### <EyeOff size="16" class="inline-block" style="margin-bottom: 2px" /> Hide/unhide
-
-Toggle the visibility of the selected file items on the map.
-
 ### <Plus size="16" class="inline-block" style="margin-bottom: 2px" /> New track

 Create a new track in the selected file.
@@ -42,6 +38,17 @@ Additionally, the selection must be a single file.

 </DocsNote>

+### <Plus size="16" class="inline-block" style="margin-bottom: 2px" /> New route
+
+Create a new route in the selected file.
+
+<DocsNote>
+
+This action is only available when the tree layout of the files list is enabled.
+Additionally, the selection must be a single file.
+
+</DocsNote>
+
 ### <Plus size="16" class="inline-block" style="margin-bottom: 2px" /> New segment

 Create a new segment in the selected track.
@@ -53,14 +60,23 @@ Additionally, the selection must be a single track.

 </DocsNote>

+### <ArrowRightLeft size="16" class="inline-block" style="margin-bottom: 2px" /> Convert to route/track
+
+Convert the selected routes to tracks, or the selected tracks or segments to routes.
+Since a route has a single segment, a track with multiple segments is converted into one route per segment.
+
+When the selected files contain only routes, or only tracks, you can also convert all of them at once.
+
+<DocsNote>
+
+Except for whole files, this action is only available when the tree layout of the files list is enabled.
+
+</DocsNote>
+
 ### <FileStack size="16" class="inline-block" style="margin-bottom: 2px" /> Select all

 Add all file items in the current hierarchy level to the selection.

-### <Maximize size="16" class="inline-block" style="margin-bottom: 2px" /> Center
-
-Center the map on the selected file items.
-
 ### <ClipboardCopy size="16" class="inline-block" style="margin-bottom: 2px" /> Copy

 Copy the selected file items to the clipboard.
@@ -15,6 +15,10 @@ The file actions menu contains a set of pretty self-explanatory file operations.

 Create a new empty file.

+### <Plus size="16" class="inline-block" style="margin-bottom: 2px" /> New route file
+
+Create a new file containing an empty [route](../gpx).
+
 ### <FolderOpen size="16" class="inline-block" style="margin-bottom: 2px" /> Open...

 Open files from your computer. 
@@ -3,7 +3,7 @@ title: View options
 ---

 <script lang="ts">
-    import { ChartArea, ListTree, Map, Layers2, Coins, Milestone, Box, Maximize2 } from '@lucide/svelte';
+    import { ChartArea, ListTree, Map, Layers2, Coins, Milestone, EyeOff, Maximize, Box, Maximize2 } from '@lucide/svelte';
    import DocsNote from '$lib/components/docs/DocsNote.svelte';
 </script>

@@ -19,7 +19,7 @@ Hide the elevation profile to make room for the map, or show it to inspect the c

 Toggle the tree layout for the [file list](../files-and-stats).
 This layout is ideal for managing a large number of open files, as it organizes them into a vertical list on the right side of the map.
-In addition, the file tree view enables you to inspect the [tracks, segments, and points of interest](../gpx) contained inside the files through collapsible sections.
+In addition, the file tree view enables you to inspect the [tracks, segments, routes, and points of interest](../gpx) contained inside the files through collapsible sections.

 ### <Map size="16" class="inline-block" style="margin-bottom: 2px" /> Switch to previous basemap

@@ -38,6 +38,14 @@ They are displayed for the current selection, like the [elevation profile](../fi

 Toggle the visibility of direction arrows on the map.

+### <EyeOff size="16" class="inline-block" style="margin-bottom: 2px" /> Hide/unhide
+
+Toggle the visibility of the selected file items on the map.
+
+### <Maximize size="16" class="inline-block" style="margin-bottom: 2px" /> Center
+
+Center the map on the selected file items.
+
 ### <Box size="16" class="inline-block" style="margin-bottom: 2px" /> Toggle 3D

 Enter or exit the 3D map view.
@@ -16,7 +16,7 @@ This tool allows you to extract [tracks (or segments)](../gpx) from files (or tr
    <Extract class="text-foreground p-3 border rounded-md shadow-lg" />
 </div>

-Applying the tool to a file containing multiple tracks will create a new file for each of the tracks it contains.
+Applying the tool to a file containing multiple [tracks or routes](../gpx) will create a new file for each of the tracks and routes it contains.
 Similarly, applying the tool to a track containing multiple segments will create (in the same file) a new track for each of the segments it contains.

 <DocsNote>
@@ -10,11 +10,11 @@ title: Merge

 # <Group size="24" class="inline-block" style="margin-bottom: 5px" /> { title }

-To use this tool, you need to [select](../files-and-stats) multiple files, [tracks, or segments](../gpx).
+To use this tool, you need to [select](../files-and-stats) multiple files, [tracks, segments or routes](../gpx).

 - If your goal is to create a single continuous trace from your selection, use the **Connect the traces** option and validate.
- The second option can be used to create or manage files with multiple [tracks or segments](../gpx).
-Merging files (or tracks) will result in a single file (or track) containing all tracks (or segments) from the selection.
+- The second option can be used to create or manage files with multiple [tracks, segments or routes](../gpx).
+Merging files (or tracks) will result in a single file (or track) containing all tracks and routes (or segments) from the selection.

 <DocsNote>

@@ -27,6 +27,6 @@ To split the selected trace into two parts, click on one of the split markers di
 To split at a specific point of your choice, hover over the trace on the map.
 Scissors will appear at the cursor position, showing that you can split the trace at that point.

-You can choose to split the trace into two GPX files, or to keep the split parts in the same file as [tracks or segments](../gpx).
+You can choose to split the trace into two GPX files, or to keep the split parts in the same file as [tracks, segments or routes](../gpx).

 <DocsImage src="tools/split" alt="Hovering over the selected trace turns your cursor into scissors." />