This object is in archive!
Shaping points to be preserved in export-Import on Android
Answered
I am planning routes on my tablet, wheras for navigation I am then using my smartphone.
Quite often, when on the road, I would need to modify the route due to current conditions.
But the track does not contain any shaping point. So this is nearly impossible with an, let's say, 80 km track
Is there a way to preserve the shaping points? Did I miss something?
The same question
There is this issue some other people also have https://help.locusmap.eu/topic/26347-shaping-points-get-lost-from-saved-route-planner-tracks
Alternatively you can add shaping points, albeit not very intuitevely. In the route planner tap the route in the place you want to add a point to - tap trackpoint info icon in the upper right corner of the segment panel - "convert" the point the a shaping one. See screeshot.
There is this issue some other people also have https://help.locusmap.eu/topic/26347-shaping-points-get-lost-from-saved-route-planner-tracks
Alternatively you can add shaping points, albeit not very intuitevely. In the route planner tap the route in the place you want to add a point to - tap trackpoint info icon in the upper right corner of the segment panel - "convert" the point the a shaping one. See screeshot.
You are right. I assumed you use the same device. But then, I often do route planning on the locus web and then share the track to my phone (basically export and import it again, I suppose) and some shaping points are randomly preserved while some are not. So maybe this is a part of the same issue.
You are right. I assumed you use the same device. But then, I often do route planning on the locus web and then share the track to my phone (basically export and import it again, I suppose) and some shaping points are randomly preserved while some are not. So maybe this is a part of the same issue.
Hi Walther,
shaping points are preserved only in routes that are planned in the Locus Map route planner because they are proprietary for this particular app. Imported routes do not contain shaping points. When you want to re-route an imported route, open it in Locus route planner. Locus adds random shaping points to it and the segments between are in manual mode. Change the mode to the desired routing profile and re-plan the route.
Hi Walther,
shaping points are preserved only in routes that are planned in the Locus Map route planner because they are proprietary for this particular app. Imported routes do not contain shaping points. When you want to re-route an imported route, open it in Locus route planner. Locus adds random shaping points to it and the segments between are in manual mode. Change the mode to the desired routing profile and re-plan the route.
@Michal Stupka
As already written, loading a track into the planner works and this also creates shaping points (SP). These are displayed as manual. Why ?
If I then go to regenerate the track is created but to a large extent on other ways.
This is because the planner creates too few SP. Here should be created significantly more. Rather clearly too much than too little. It is not much memory. or are there any other disadvantages with a lot of SP?
@Michal Stupka
As already written, loading a track into the planner works and this also creates shaping points (SP). These are displayed as manual. Why ?
If I then go to regenerate the track is created but to a large extent on other ways.
This is because the planner creates too few SP. Here should be created significantly more. Rather clearly too much than too little. It is not much memory. or are there any other disadvantages with a lot of SP?
@Michal Stupka
Another problem is that the route is calculated differently in some places even with more SP. But this can not be avoided. But after the recalculation I don't know where the old route was and therefore I can't detect any deviation.
Therefore, the old route should be displayed as yellow in the background. So it is only visible where the deviates. And I can rework there.
If a red exclamation mark appears at the places, that would be great. Whether this is technically feasible I do not know.
Should I create a proposal or do they implement it right away ? If yes how should I call it.
After saving, the yellow (old) can then be deleted
@Michal Stupka
Another problem is that the route is calculated differently in some places even with more SP. But this can not be avoided. But after the recalculation I don't know where the old route was and therefore I can't detect any deviation.
Therefore, the old route should be displayed as yellow in the background. So it is only visible where the deviates. And I can rework there.
If a red exclamation mark appears at the places, that would be great. Whether this is technically feasible I do not know.
Should I create a proposal or do they implement it right away ? If yes how should I call it.
After saving, the yellow (old) can then be deleted
Hello Walter, others
am I understanding correctly, that you plan routes on a tablet and then transfer them over GPX files into your phone? Not just the original plan is lost, but also some other metadata. The best, how to do this is using the sync system of Gold Premium, which preserves all data because it transfers identical routes/points to what is stored in the database.
Support for "shaping points" in GPX is simply complicated for me. Shaping points are not directly included in the route. The whole plan is one big JSON file stored separately so it is hard to export to GPX as well. I really hope this won't be necessary to do.
Hello Walter, others
am I understanding correctly, that you plan routes on a tablet and then transfer them over GPX files into your phone? Not just the original plan is lost, but also some other metadata. The best, how to do this is using the sync system of Gold Premium, which preserves all data because it transfers identical routes/points to what is stored in the database.
Support for "shaping points" in GPX is simply complicated for me. Shaping points are not directly included in the route. The whole plan is one big JSON file stored separately so it is hard to export to GPX as well. I really hope this won't be necessary to do.
Replies have been locked on this page!