[mkgmap-dev] r3165 in via_ways branch

Thu Apr 3 09:42:57 BST 2014

Hi Gerd,
I haven't really understood what the via ways branch is doing...

Could you explain it again?
Is it only about restrictions?

What could really improve the maps for me would be short invisible short 
via ways on all intersections in order to reduce the turn angle...
So instead of

       |
       |
-----|------
       |
       |

make every intersection (on those places where the angle is over 60°) 
look like
       |
    / | \
-----|------
    \ | /
       |

Basically building short invisible via ways (if invisible routing lines 
are not what this is about, then just give a style/command option 
possiblity to define the type and then set it invisible in the typfile) 
for routing (basically the same as highway junctions are in reality, 
just smaller but serving the purpose of having no sharp turn angle).
I'm pretty sure this would improve routing a lot for my maps, but this 
is only an assumption as I cannot build large maps to try it out... (the 
via ways should'nt be straight as in the above example but of course 
round to minimize the angle. Length of 10m is long enough - so make em 
consist of 3-4 points).

On 03.04.2014 09:28, Gerd Petermann wrote:
> Hi all,
>
> I think r3165 is ready for a deeper test.
> Changes compared to trunk:
> - handling of RouteRestrictions was mostly rewritten to make sure that 
> mkgmap doesn't
> write wrong restrictions to the img file (this was possible when 
> different roads connected the same points
> with direct arcs)
> - added support for restrictions with one via way (see below)
> - added support for tag type=restriction:*  , e.g. 
> type=restriction:motorcar
> - added support for tag restrection:*=<turn> , e.g. 
> restriction:motorcar=only_left_turn
> - added support for no_entry and no_exit restrictions
> - improved log messages for invalid or possibly obsolete restriction 
> relations
>
> Reg. via ways:
> According to NodCheck in the display tool the data written by mkgmap 
> r3165 is correct,
> but I found no effect on routing :-(
> Up to now mkgmap adds a 4 node restriction to both end points of the 
> via way.
> Maybe there is a bit in a header which has to be (un)set, but I can't 
> find any.
> Multiple via ways are not yet supported, but partly verified to be 
> correct.
> Maybe I'll look at that when we see an effect on routing for a single 
> via way.
>
> @Steve: Do you see any effect of them in your maps?
> If yes, what might be wrong with the data written by mkgmap?
>
> Gerd
>
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- 
keep on biking and discovering new trails

Felix
openmtbmap.org & www.velomap.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140403/4caa01a5/attachment.html>