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

Tue Mar 3 08:26:00 GMT 2015

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

From: mike at tvage.co.uk
To: mkgmap-dev at lists.mkgmap.org.uk
Date: Mon, 2 Mar 2015 22:46:07 +0000
Subject: [mkgmap-dev] --make-opposite-cycleways option

Dear all,

When using the --make-opposite-cycleways option, I notice that the address
index adds a road name of the actual road name suffixed with " (cycleway)".
For me at least, this is undesirable. Also the generated name does not
conform to the OSM naming convention of not including any descriptive
information in names. I therefore propose that the name of an opposite
cycleway be set to the same as the original road name, and that users who
want to name the opposite cycleway differently should use the style file to
rename it.

In looking at the code that produces the opposite cycleway, I also believe
there is an error in the way it handles access tags - the code currently
sets access=no, bicycle=yes and foot=no, but ignores all other access tags.
Hence if (for example) the road has psv=yes on it, the generated cycleway
will also have psv=yes (unless I am misunderstanding something in the
handling of access tags). 

I therefore submit the attached patch for trial.

Regards,
Mike

_______________________________________________
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/20150303/1804e291/attachment.html>