Importing a route is kinda useless

[thany]

I tried importing a previously created route, in hopes to make some tweaks. Nope. When I import a route, it's just sort of there. It's just decoration. Can't do anything with it. Would be nice if I could click it and change the start/finish points or something.

[mjaschen]

I guess you used “Load Tracks” instead of “Load Tracks as Route”. While the former feature just create a “dumb” overlay, the latter creates a fully customizable route.

Besides that: the proper way to work on previously created routes is to use the permalink, i.e. the link from the browser's address bar as it contains all information to fully define a route.

Hope that helps.

[thany]

Ah right, I see.

In my mind an export-and-then-import ideally shouldn't loose information, and when using KML it doesn't need to either. I think the important bit is the waypoints used to tweak a route, and it might be possible to include those in a KML export as some kind of vendor-specific metadata.

As for the "dumb overlay" as you call it, I still fail to see what the intended purpose of such a feature is. Maybe only if this tool is used for presentation purposes, but even then I'd expect a tooltip on an imported route at the very least.

[EssBee59]

Sorry, in my opinion the import functions are very very usefull!!!!!!!

Yes, for an optimal usage, basic knowledges (actually only the differences betweent track and route!) are prerequisited, but it is very easy to learn the usage of the brouter-web import-functions...

-with "Load tracks" you only show the corresponding track on your display
(as example, it helps if you want to create a new track which should not use the same route, or or or...)

-with "Load track as route" a "reverse routing" occurs (from thausends of track-points only the significant route-points remain)
A-using the option "tuning /fuzziness" the number of route points can be defined (minimum start and end point, maximum is the limit of brouter some hundreds)
Depending on what you intent to do, you set the fuzziness....
==> "low", you get a lot of route-points and will not loose information by re-export, but you can not easylly change the route!
==> "high", you get only few route-points: changes of the route is easy, but, if you do not want modifications of the route, you should select the "right" profile (ideally the profile used to create the initial track).
As explained, as route-points are now used, a new route-calculation is necessary to get a new track!
Regards
EssBee

[nrenner]

In my mind an export-and-then-import ideally shouldn't loose information

Saving and reloading routes is not yet implemented, see #16.

As for the "dumb overlay" as you call it, I still fail to see what the intended purpose of such a feature is.

This is mostly meant for GPS recordings, e.g. to see where you previously have or have not yet been and to manually plan a new route with a previous trace as a guide in the background. Yes, this is still very basic with lots of room for improvements, but well...