Hi Felix,
if your style interprets a tag like a oneway=yes you should add
that tag. This might prevent problems caused by the RoadMerger,
which might reverse lines which are not oneways.
If you find or set oneway=-1, the current implementation
will reverse the way.
If you add multiple routable lines for one OSM
way, one with, one without the oneway tag,
you will see unpredictable directions if such a way
is modified by the WrongAngleFixer and the type
is direction dependent.
The WrongAngleFixer assumes that the points in
all ways with the same OSM id are equal, so
it optimizes one way and copies the points to the others.
This will fail if they have different oneway attributes.
If you think this could be the cause of the problem,
I should be able to provide a fix.
Gerd
Date: Fri, 25 Apr 2014 01:00:18 +0800
From: extremecarver@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] oneway reverse patch
Ups - but forgot to say. I think in 99% of all cases - cycleway:left and cycleway:right are used on streets which feature oneway=yes... less often oneway=-1 and even less often no oneway at all.
Streets with oneway=yes are fine. I'm talking about no oneway tag from OSM data at all, or oneway=-1 set in style (but no oneway from OSM data) or no oneway at all. Only on those there are problems - so you're not likely to notice them I think....
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev