Yes - I think for the start and end of a route - the algo will choose topmost route only. For inbetween sections however not - there it chooses the best - at least according to my tests a few years ago...
There is a max of 6 or 7 roads lying on top of each other - if more it will produce a routing error and not go there at all.

And yeah - I also don't know what's best. V2 seemed best to me so far.

On 5 September 2015 at 15:09, GerdP <gpetermann_muenchen@hotmail.com> wrote:
Hi Felix,

okay, I came to similar results with other styles today, so
maybe I'll revert the change that makes most angles larger.

Reg- --x-cycle-map:
Without it only angles < 45° are changed to 45°.
With it and v2, angles were changed to 68° when road speed of an arc is >= 3
and 90° when road_speed >= 5.
With it and v3, all angles < 90 are changed at junctions with only 3
directions.

I think the Garmin algo is not really able to handle multiple arcs with
that your style creates, at least it doesn't seem to "look" at all of them,
esp. the last part of a route seems always to use the "topmost" road,
means, the one that was last added in the style (as long as the selected
vehicle is allowed).
I think we first have to understand how the Garmin algo works before
we can try to manipulate the data for better results.
This is time consuming and error prone, so I'll need a few more days to
work out facts.

Gerd


Felix Hartmann-2 wrote
> Well - I guess this will never be without errors - with Patch v3 there
> is again a little loop - now again at the first place:
>
>
> (only happens with "Shorter Distance" and one of the
> driving/motorcycle/Dirtbike and so on profiles..).
>
> Also on some other places still detours - in general "Shorter Distance"
> seems to be much more problematic than "faster time". So for sharp turns
> - ironically - shorter distance chooses the detour to avoid the sharp
> turn.
>
>
> I'm not really sure patch v3 is better than v2 however. Results are
> 50/50 better/worse. However the arrival times got a bit slower (even if
> following exactly the same route). I always tried with --x-cycle-map
> switch - never without. I'm still not so sure what this option really
> changes for outcome in the end.
> So - additional intersection roads would still be king IMHO... (but yes
> I know - not possible).
>
>
>
> On 04.09.2015 19:34, Gerd Petermann wrote:
>> Hi all,
>>
>> attached is v3, only small changes:
>> 1) the message "maybe duplicated OSM way " was printed too often
>> 2) with --x-cycle-map, change the headings
>> at junctions with only three different arcs so that angles of 90° or more
>> are created.
>>
>> If I hear no complains I'll commit this patch on monday,
>> probably without the --x-fix-sharp-angles switch.
>>
>> I am still trying to work out in what case the Garmin routing algo
>> prefers a detour, so maybe I find more improvements later.
>>
>> Ciao,
>> Gerd
>>
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>>

> mkgmap-dev@.org

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
> --
> keep on biking and discovering new trails
>
> Felix
> openmtbmap.org & www.velomap.org
>
>
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev@.org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
> ajjdjdgb.png (24K)
> <http://gis.19327.n5.nabble.com/attachment/5854037/0/ajjdjdgb.png>





--
View this message in context: http://gis.19327.n5.nabble.com/Patch-v3-sharp-angles-tp5853996p5854043.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



--
Felix Hartman - Openmtbmap.org & VeloMap.org
Floragasse 9/11
1040 Wien
Austria - Österreich