
Hi , the current wiki http://wiki.openstreetmap.org/wiki/Relation:restriction#Tags documents these restriction texts: no_right_turn / no_left_turn / no_u_turn / no_straight_on / only_right_turn / only_left_turn / only_straight_on / no_entry / no_exit current mkgmap allows typos like no_turn_right , no_turn_xyz (anything that starts with no_turn) as well as all strings that start with only_turn It prints a warning for them, but doesn't ignore them. I found 14 no_turn_on_red restrictions like this: http://www.openstreetmap.org/relation/2033334 which probably should not be interpreted like normal restrictions, so I think mkgmap should not accept generics. OK? Gerd
Date: Sun, 13 Apr 2014 13:23:35 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] restriction relations with wrong restriction text
On Sun, Apr 13, Gerd Petermann wrote:
Hi all,
should mkgmap ignore if a no_left_turn restriction doesn't describe a no_left_turn?
For example, look at this http://www.openstreetmap.org/relation/3414378
That's around the corner of my old flat, I know the area very well. The text is correct, the to way is wrong. I will fix that. I think in such cases you should ignore the restriction and print a warning, so that people can fix it.
In short: the restriction should be ignored after printing a warning.
Correct.
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev