Faster sharing of a GPX
Completed
I mainly use LM on the road to plan tours, especially with Bikerouter. When I calculate a route, I always have to save it first, then search for the saved track in my library and only then can I send it to my bike computer as a GPX via Share. It would be cool if I could send the route directly after searching for a destination. Or if I didn't have to save the route in the route planner first, but could share it directly as a GPS after the calculation. This would be much faster and my library would not be filled with routes that I no longer need.
I like this idea 
Hello Jan,
I'm not convinced that this is so common use case, that extra direct button in the menu make sense.
But maybe this will be faster than your current steps.
Simply
Better?
Hello Jan,
I'm not convinced that this is so common use case, that extra direct button in the menu make sense.
But maybe this will be faster than your current steps.
Simply
Better?
OK, looks like the way I was looking for. But: LM is crashing when tapping "Route details".
I'm using LM on Samsung Galaxy S21 FE with the last versions of Android and LM.
OK, looks like the way I was looking for. But: LM is crashing when tapping "Route details".
I'm using LM on Samsung Galaxy S21 FE with the last versions of Android and LM.
Crashing? Eh.
You have a visible planner route on the screen and a simple tap on the "Route details" causes the crash?
Are you able to create and share a bug report with me? In Crashlytics (an automatic system for crash reporting), I saw no crash on S21 during the last hour. Or it is possible that the crash was caught by the app and stored in the Locus/logs directory. But this is accessible only over PC on modern Android phones. Thanks a lot!
Crashing? Eh.
You have a visible planner route on the screen and a simple tap on the "Route details" causes the crash?
Are you able to create and share a bug report with me? In Crashlytics (an automatic system for crash reporting), I saw no crash on S21 during the last hour. Or it is possible that the crash was caught by the app and stored in the Locus/logs directory. But this is accessible only over PC on modern Android phones. Thanks a lot!
Exactly when taping "Route details". You got mail from ...k01.de
Exactly when taping "Route details". You got mail from ...k01.de
As I see, my last reply wasn't saved. Maybe it even does, sorry for duplicate.
Yes,the simple tap on "Route details" causes the crash.
You got mail from ...k01.de
As I see, my last reply wasn't saved. Maybe it even does, sorry for duplicate.
Yes,the simple tap on "Route details" causes the crash.
You got mail from ...k01.de
Thanks, bug report received. Seems to be a common problem when the track is too large. I have to improve it finally. Give a try to the shorter track ...
Thanks, bug report received. Seems to be a common problem when the track is too large. I have to improve it finally. Give a try to the shorter track ...
Crashes at about 200 km. 192 worked, 201 not.
Crashes at about 200 km. 192 worked, 201 not.
I can say, this is, what I was looking for. Now it's on you to make the planning and gpx-sharing of routes >200 km possible ;)
I can say, this is, what I was looking for. Now it's on you to make the planning and gpx-sharing of routes >200 km possible ;)
Perfect. I'll look at it.
Perfect. I'll look at it.
I still have one wish for this feature. If I share the planned track in this way, the track and the GPX will be named "Temporary_route". Could the name perhaps also consist of start and destination? I am aware that this is difficult if the start or destination is outside a town or city. But with several tracks created in this way, it is difficult to keep them apart.
I still have one wish for this feature. If I share the planned track in this way, the track and the GPX will be named "Temporary_route". Could the name perhaps also consist of start and destination? I am aware that this is difficult if the start or destination is outside a town or city. But with several tracks created in this way, it is difficult to keep them apart.
Replies have been locked on this page!