[mkgmap-dev] [PATCH] RoadMerger reverses roads

Sun Jan 12 15:11:51 GMT 2014

Hi Minko,

I see no problem as long as the bitmap for the routable way is not direction depended.
The order of processing is now this:
for one OSM way your style adds 
- one or more routable ways 
- one or more non-routable ways
For each of them mkgmap creates a copy of the list of points
and reverses the points for the oneway=-1 or oneway=reverse ways.
Later, the routable ways are passed to the routine that removes
short arcs or wrong angles. If the first one is changed by that routine, all 
other copies are changed as well to make sure that all copies
are displayed at the same position.
Next, the routable ways are passed to the road merger,
the non-routable ways are not touched by the road merger
or any other routine like the ones that splits roads  with loops.
As long as we keep that order it should work, allthough
the splitting sometimes adds points which may cause small differences
between the displayed road and the overlay lines.

Gerd

> Date: Sun, 12 Jan 2014 15:45:14 +0100
> From: ligfietser at online.nl
> To: mkgmap-dev at lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] [PATCH] RoadMerger reverses roads
> 
> Gerd, I dont create a routable way for those items, but I dont know if the orientation will be different for the rendering if the way is reversed in direction.
> I assume left would become right, so a left sided bike lane would turn up on the right side?
> 
> > If you create routable ways for them I think it patch will cause
> > trouble.
> > Maybe we need a tag like mkgmap:reversible=no tell the road merger
> > that this road is not
> > a oneway but still has a direction?
> > 
> > Gerd
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140112/944883bd/attachment.html>