Improved Import of GPX files | Verbesserter GPX Import

We just launched an improved import for GPX files on the Kurviger website.

  • If your file contains multiple routes / tracks, you can now select which of these should be imported
  • Improved support for special Garming GPX files (for example recognize Garmin ShapinPoint extension)
  • Importing multiple Track segments in GPX files

You can give this a try here. Please let us know if something suddenly doesn’t work anymore.


Wir haben gerade einen verbesserten Import für GPX-Dateien auf der Kurviger-Website eingeführt.

  • Wenn deine Datei mehrere Routen/Tracks enthält, kannst du jetzt auswählen, welche davon importiert werden sollen
  • Verbesserte Unterstützung für spezielle Garming GPX-Dateien (z.B. Garmin ShapinPoint-Erweiterung erkennen)
  • Importieren mehrerer Track-Segmente in GPX-Dateien

Du kannst den neuen Import hier ausprobieren. Bitte lass uns wissen, falls etwas plötzlich nicht mehr funktioniert.

8 Likes

Wunderbar!!
Habe das gleich mit einem ACT ausprobiert, klappt wunderbar! Brauche nicht erst Basecamp zu öffnen um Track für Track zu speichern!

6 Likes

Heb het uitgeprobeert en het werkt prima. Bedankt!

2 Likes

Mega! Danke dafür! Genau das habe ich vor ein paar Wochen gesucht, als ich meine alten Garmindateien verwenden wollte. Wenn man noch das automatische neu berechnen ausschalten könnte, wäre es perfekt.

1 Like

Also du kannst die Dateien auch als Overlay laden: Overlay-Manager [Kurviger Knowledgebase]

Dann wird nichts verändert, beim Routen-Import versuchen wir aus den gegebenen Daten eine Route zu berechnen.

A post was split to a new topic: Importing multiple tracks and save them automatically

I am currently planning a Trip to Scotland and for starters I have imported a number of GPX tracks and routes from different sources (i.e., in quite diverse GPX formats). I would like to share my thoughts about potential points of improvement within new import.

  1. Importing from multitrack GPX - being able to select desired contents frim a multitrack GPX is a game changer compared to tge past, however it gets a bit annoying when you have to select the same file more than 15 times in a row, because it contains many contents that need to be imported separately. Some kind of batch import (e.g. opening one browser tab for each selected track) or at least remembering the file used for the last import would be beneficial.
  2. Filename in Kurviger Cloud - when importing from a multitrack GPX, it would be helpful to add the selected track name as a suffix to the default file name used for saving in cloud
  3. Import waypoints as Favourites i have noticed that importing WPs (and even routes) from a GPX sometimes causes erratic results when combined with importing tracks. This may be due to WPs not always being located on the roads and the track not reaching them. Those waypoints sometimes do contain useful POI information which gets lost when importing only a track. It would be helpful to be able to import the WPs from the GPX to the Favourites in the same step when you import the corresponding track and save some time and manual effort to repeat the process separately.
  4. VPs in manual optimization when importing a track and after the “shapepoint optimization” usually there is a need to manually optimize around 10 SPs. Some of those are leading to a remote POI and cause a turnaround - those are obviously VPs and will cause a turnaround warning after the import which would need to be treated by converting the SP to VP. It would be good, if user could set a VP instead of SP already during manual optimization and therefore avoid having to revisit the same point again after the import to remove the warning.
  5. WP close to a junction - i have already written about this before, but I will repeat myself after experiencing how annoying this really is when importing some 30 tracks. When importing tracks, there are usually hundreds of WPs available and the optimization algorithm often selects those that are close to a junction which cause some 20ish warnings directly after the import which again have to be reviewed by the user and in most cases just shifted manually a couple of millimeters. Please combine the two algorithms (SP optimization and junction detection) to avoid unnecessary manual work.
  6. “Use only Beelines” option for GPX tracks that include predominantly off-road sections it would be helpful to import them only connected with beelines for starters. This may often be a much better starting point than having an “optimized route” where you would have to change many sections to beeline manually to make it work.

That’s it - for now.

3 Likes

Thanks for the feedback.

We will have a look. I can’t really envision how this would work without possibly feeling weird.

Right, if the track or route has a name, we should use that name of the route / track in the GPX file. Not sure if we should generally add something to the name.

You can import them as overlay or favorites, depending on your needs. I am not sure this needs to happen in one step though (you can for overlays).

Usually, WPs that are in the file should be threated as VP in the import by default. Isn’t this the case in your example? We explicitly limited the route planning part during the import to have a clear separation between the two workflows.

We will have a look :+1:. Can you provide us with a sample where this is particularly an issue?

Makes sense :+1:.

Idea #1: Remember the filename, then it would look something like this (import buton and the checkbox would need to be added:

the above picture is actually a :cockroach:, because using “Back” button in the browser, I could also produce following situation, which is surely not processing all the listed files:

Idea #2: Open additional tab for multiple import. This one would also need an additional checkbox or button which would allow you to clone the the tab in which you already selected the file. You would then proceed to import and optimize one track and when you finish saving the file, you could close this tab, move to the next one and select-optimize-import-save the next track. Also in this second tab you could apply “clone” and create third tab and so on… This of course assumes that you are working in the browser, not in the app, but I assume such complex imports are mostly better done on the browser.

Idea #3: Open one tab per track this one might feel weird, but still an idea. When you select for example 5 tracks to be imported and tick the checkboix “Each track in separate tab” - the app opens aditional 4 tabs with each tab containing one different track that would be imported. Also this idea assumes import using browser.

Ok, now that I have done my imports, this use case might not come in the next couple of months for me… I guess in general it is not needed very often and It is probably not worth spending much of your time on it, but if you see some “low hanging fruits” - it would be appreciated…

My proposal:

  • for import from Multitrack-GPX: “_” (if several tracks are imported at once - just the name of the first from currently selected tracks)
  • for GPX containing single track/route - only “”

I had a second look - maybe the issue is not that extreme as I have perceived it due to importing a lot of GPX files in a short time. It is also a bit exaggerated by the manual corrections - when I add shaping points in manual optimization, I also create some warnings myself. I will send you the examples via private message.

I was thinking about these “individual points without order” - if these could go maybe directly to favorites, because I do not know what would be their contribution to the route if there is no order…
But again - probably not worth spending the development time on it - it appears to be an edge case.

1 Like

Just some thoughts. I tried with a file with multiple routes and tracks (I found no file with free waypoints), and simple gpx exported from Kurviger in all possible variants. Tested on smartphone.

When I click on a gpx-file Kurviger opens the Import-Manager, I can select or deselect the waypoints, routes tracks. Then I start the import with or without route optimization (I guess most prefer to optimize the route). So far so good, known and works fine.

There was a discussion here where importing the tracks (here from Calimoto, but also from any other app) is a challenge and possibly a showstopper for them to use Kurviger. Using overlays is always possible, but additional handling of files = uncomfortable.

So it is first about mass import. “Easy” case is simple gpx. Then such complex files with multiple waypoints, routes and tracks, each element can be separate or related to each other (for example 5 WP, 1 route, 3 tracks).

When I want to make a mass import, I do not necessarily want to optimize the route now! I can do this whenever I have time or when needed.

The motivation is primary to have it the cloud, as everything is in one place and very comfortable.


Second is route optimization. Today it is included only in the import manager. As I remember it is on the list to also make it available for the current planned route. If this would be available, I guess it could also help here.


Workflow could be realized by some “wizard” guiding me through the steps, over several pages (as required). No need to clutter one page with checkboxes, options and checkboxes.

The wizard should allow as input more than one file or a zipped file. On web perhaps even drag and drop onto the wizard.

This wizard could offer the options to “Import now + Optimize”, which ends the wizard (more or less as today). This should only be possible with a single and a simple (no complex) file? Also an option to “Save to Folder”.

In case of a zipped file or multiple files or a complex file the wizard could run a loop for each file or included wp, route, track. Option to “Save to folder”, but not a option to optimize or import anymore.


The “Save to folder” is surely a challenge, dependant on free waypoints, routes and or tracks, a simple or complex gpx. The user could be asked for a folder name, which is created. As alternative the user chooses an existing one.

Folders containing only tracks is today not possible, so would be also a prerequisite, I guess. Would also mean, that a imported, saved track can be loaded as route.


Shorter: I think some steps could be done first, like Folders containing tracks (including moving ridden ones into these), Route optimization also for planned routes. Then a wizard, which supports import of single and multiple files in all useful levels of complexity.

Perhaps first with focus on simple gpx to support users coming from other apps.

For complex files, behave like today and error message “Please import file xxx as single file” and adding one proposal from @t00thl355, e.g. remember file.

Yes I think something like this would be the way to go here and then store all routes into one folder of the cloud.

I think an optimization at a later stage is not great, because then you have “random stuff” in your cloud.

Still, it is hard to imagine the whole flow, without overcomplicating things :frowning:

No worries :wink: - I know the feeling. With every use case, it’s always the question, should we introduce the complexity vs. some more manual labor on the user side and keep the UI lighter. How often do you import files like this and how often are you using the current way etc.

I’ll have a look thanks :slight_smile:

Yes, so for random points, the idea was to use them in the overlays and only keep your actual favorites in the favorites :slight_smile:.