I also reported the possible way to solve this as Idea first, but its more a big Problem for me.
The variable "Route interpolation Step" is used for Manual drawn routes while planning them. But while saving there is still a fixed constant of 100m used.
So if i set the Variable "Route interpolation Step" to 20m, I see a 20m interpolated Height-Profile while planning. But while Saving the Route, a fixed constant of 100m is used und many points get lost.
Because the variable in ExpertSettings is normaly also set to 100m, it would not change anything for normal users.
I think its the correct way to also use seh variable "Route interpolation step" instead of the fixed constant of 100m while saving a Manual route.
Its a just win situation...
I like this idea 
Thanks for the answer. Yes, I was also thinking about this another option > checkbox to save interpolated data.
---
Little later: oki. Probably the best solution for now. I do not want to break current functionality, so new settings will be added in the next Locus Map Pro/4 versions. Thanks for the idea.
Menion
Thanks for the answer. Yes, I was also thinking about this another option > checkbox to save interpolated data.
---
Little later: oki. Probably the best solution for now. I do not want to break current functionality, so new settings will be added in the next Locus Map Pro/4 versions. Thanks for the idea.
Menion
Hello Markus,
it is not so simple as it looks. Interpolation parameter is used really only in the route planner screen. When the track is saved, all manual segments are replaced by a straight line. So the behavior will! change in case, the parameter will be used upon saving.
So here come my worries, if this change causes any problems with export/navigation etc. What is the reason you need this change?
Hello Markus,
it is not so simple as it looks. Interpolation parameter is used really only in the route planner screen. When the track is saved, all manual segments are replaced by a straight line. So the behavior will! change in case, the parameter will be used upon saving.
So here come my worries, if this change causes any problems with export/navigation etc. What is the reason you need this change?
Yes i understand. I think if a special user change this Variable, then this user also want to save this additional points. Maybe we can mark this Points as interpolated points. (but not necessary)
Ok... first the interpolation step was fixed to 100m. We changed this to a variable in expert Settings.
Now for saving the Manual drawn Route we have again a fixed 100m step.
Yes if someone changes the Variable in Expert Settings, then this person Want tighter Interpolation and more saved Points.
Specially for users which go Ski-Mountaineering, We need tight height interpolation for a profile.
Drawing a manual Route and Saving it should be same.
And again, if a user let this Variable at 100m, then it is like always bevore. (100m variable is same as 100m constant)
On straight Lines, the interpolation is necessary for Height Profiles. And in future, we will have much tighter height data available all over.
We use Locus now in our Mountain Rescue Team. And therefore i made OSM Data high dense in our region. And use Height Data with 3m point density. So we get Maps of 1:5000 or 1:1000.
greets Markus
Yes i understand. I think if a special user change this Variable, then this user also want to save this additional points. Maybe we can mark this Points as interpolated points. (but not necessary)
Ok... first the interpolation step was fixed to 100m. We changed this to a variable in expert Settings.
Now for saving the Manual drawn Route we have again a fixed 100m step.
Yes if someone changes the Variable in Expert Settings, then this person Want tighter Interpolation and more saved Points.
Specially for users which go Ski-Mountaineering, We need tight height interpolation for a profile.
Drawing a manual Route and Saving it should be same.
And again, if a user let this Variable at 100m, then it is like always bevore. (100m variable is same as 100m constant)
On straight Lines, the interpolation is necessary for Height Profiles. And in future, we will have much tighter height data available all over.
We use Locus now in our Mountain Rescue Team. And therefore i made OSM Data high dense in our region. And use Height Data with 3m point density. So we get Maps of 1:5000 or 1:1000.
greets Markus
Perfect solved. Interpolation is held as Interpolation Points. (No additional Routepoints)
Thanks for working on it. Works as i wished. 😁
Now Terrain can be analyzed. and Saved with the Cut Profiles. (if you use high density Height Model .hgt)
Perfect solved. Interpolation is held as Interpolation Points. (No additional Routepoints)
Thanks for working on it. Works as i wished. 😁
Now Terrain can be analyzed. and Saved with the Cut Profiles. (if you use high density Height Model .hgt)
Replies have been locked on this page!