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: [email protected]
To: [email protected]
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....



On 25 April 2014 00:39, Minko <[email protected]> wrote:

Yes I render cycleway:left and cycleway:right too.

And as you say, they are always on the wrong side on the GPS.

Interesting to know that Garmin uses asymmetric lines independent of the road 
direction. If we only could find out how they do this...



Felix wrote

> I don't think that Minkos style shows cycleways on the left/right side

> of a road - am I wrong? - Anyhow they would usually have a oneway tag

> already in OSM data.

> Also definitely no uphill/downhill arrows - which nearly never

> actually have a oneway tag (and only sometimes I add one during

> processing).

_______________________________________________

mkgmap-dev mailing list

[email protected]

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev




_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev                            
          
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to