Via point in "add new route"

Hi Marty

read manual, uncheck "compute instructions"

http://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning&s[]=compute&s[]=route#planing_a_route_with_brouter

I already read it, but I read the info on page you have posted again. This didn't help, because I already had "compute instructions unchecked". So I've checked it, unchecked it again, but it still does the same thing.

Hello guys,

"Via points" are added always, no matter if you "compute instructions" or not.

Anyway you may try to edit config file and it's parameter:

1. dev_enable_add_new_route_via_points

Hi there Mr. Dev., I will try that. But I am used to have between 10-30 tracks prepared on my screen at any given time, ready to choose from them which one I will ride that day. That would mean having 200-600 via points at the screen, making the screen too cluttered. And already, geocaching icons are cluttering the screen, although I welcome those. Another hundreds of icons of "Via point" is a mess.

Having just orange, 2/3 opaque track doesn't clutter it, because you can see through it and you can choose how thin the line is. Reducing the size of "Via point" icons would reduce all the other icons too. + the "via points" waypoints would remain and if I understand how it works well, the more icons Locus has to display, the slower it is. It would make sense.

So, I just wanted to explain my point of view - why someone wouldn't like them. From previous topics I've seen you respond in, I think you are open minded programmer, so just consider this and my arguments please.

Good day Marty,

similar to your idea about improving geocaching stuff - also in this case, I think that your use-case is really specific. Via-points were introduced in the middle of June if I remember correctly, and since then, you are first who complain on visible icons.

So,

1. I see no reason to change default behavior

2. you may use mentioned parameter which disable creating of via-points during "Add new route" function

What you say is true, I probably am a minority. But if anyone ever wants to remove those points, your solution with editing the .cfg file works well, so again - thanks, my problem is solved.

Hi guys.

I confirm that is a problem for me too, I was about to write the same post.

The workaround suggested by Menion is enough for me, now, and I'm about to apply in few moments (!).

Until now I solved in another way, that I'd like to suggest to Marty for existing routes.

Simply:

1. export the route with annoying viapoints;
2. import it again selecting a folder where to store waipoints to;
3. track is stored in a different folder, of course, without viapoints.

Ah, just to contribute to understand the problem:

when I create a new route I tap the screen on places I want the route pass by, but they often don't are real "via points", that is, I intend, "points where you could go another way but route you create says this is the direction" (;-)).

In most cases theese points are intended to force the algorithm to calculate THAT route, not to indicate the direction to biker/yourself (route itself is enough for it).

Am I wrong?

Yeah, something I was thinking about as well. Even though something may be a problem for people, it's not too big of a problem so they just learn to live with it - because they don't see easy solution to fix it, or they would have to ask on forums.

But the workaround worked and now it's my preferred way - I tweaked few more things in "advanced" cfg setting (show simplified up to zoom level xx), so that's something to consider as well.

However, if you tap the screen in PLACE A and then tap screen 10km away on PLACE D and it goes through the CITY B you don't like, just tap on the MINUS button and make an extra tap on PLACE C (you want to go through) in between. If it doesn't work as well, make more, shorter taps. Sometimes the track building algorithm can be a stubborn beast.

What I hate though is that (I use OSM bike Europe) on my map, I see a track. It's not a big road, just a forest track, but good for my MTB. But the track building algorithm doesn't know it and won't allow me to go through there.

1)I tried to use different Nav. data sources, to no avail. Some works in some places, others in another. The problem is when the route you are creating needs to lead through two of such places - you can choose only one "nav data source". I suppose this is not Menion's problem, but of the data sources.

2)I tried to use a trick of tapping "compute'" (which disables it), going over the problematic part manually, then enabling "compute" again and resuming the track planning. It has its problems, but who knows, maybe it works now better - it's worth trying.

Hi, Marty.

I agree with your 1 and 2 points (about 1: where do you find additional nav sources? I have, beside of online ones, BRouter and Graph Hopper. If was possible to have it in Locus, could be great to use Outdooractive algorithm, the best I know for Europe).

Strategy you describe in point 2 is the only one is possible to use, when all algorithms fail.

More: there is one better method to reach PLACE D from PLACE A going through PLACE C and not CITY B: you can drag and drop over PLACE C the red point in the middle of the pink line between point A and point D. Thiis a useful feature implemented in Locus.

But, I think, all theese things aren't problems of Menion.

Bye

Hello. It's me again. After having it working without "via points" until I updated Locus few days ago, it now adds them to my track. I went to config.cfg file to look up the line with how Menion helped me one year ago, but the line wasn't there.

My question is, how to disable adding of "via points" to my track?

Hello Marty

this was also my question and the answer from menion to me:

http://forum.locusmap.eu/index.php?topic=5417.msg45464#msg45464