[mkgmap-dev] --make-opposite-cycleways option

Tue Mar 3 08:44:06 GMT 2015

Hi Minko,

reg. broken car routing:
if I got it right, there is no way to avoid this problem completely when 
adding multiple routable ways for a single OSM way.
You either have broken car routing or broken bicycle routing, depending
on the order in which the ways are added to the net. 
Is this still correct or did you find a way to work around that problem?

Gerd

ligfietser wrote
> ----- Oorspronkelijk bericht -----
>> Van: "Gerd Petermann" &lt;

> gpetermann_muenchen@

> &gt;
>> Aan: 

> mkgmap-dev at .org

>> Verzonden: Dinsdag 3 maart 2015 09:26:00
>> Onderwerp: Re: [mkgmap-dev] --make-opposite-cycleways option
>> Hi Mike,
>> 
>> I think you are right regarding the access tags.
>> The current solution in combination with the default style
>> might route a truck through the wrong direction of a oneway.
>> Thanks for pointing this out.
>> 
>> If I got it right, most style developers don't use this option,
>> they prefer to have the logic in the rules.
>> Maybe this is another argument to remove the option
>> instead of adding code to make it work in special cases?
>> 
>> Is anybody able to change the default style so that it produces
>> the same result ?
>> 
>> Gerd
> 
> 
> Yes, we have discussed this before, I tried to add it in the styles for
> the OSM generic maps, but this resulted in wrong navigation for cars.
> The name "cycleway" in the synthetic part you can delete by this rule in
> your line style:
> 
> mkgmap:synthesised=yes & bicycle=yes { set mkgmap:highest-resolution-only
> = true; delete name }
> 
> http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2014q2/020939.html
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

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

--
View this message in context: http://gis.19327.n5.nabble.com/make-opposite-cycleways-option-tp5835586p5835618.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.