Hi Minko, the problem is caused by the merge-lines routine. You see the problem also in a map created with r2570 if you look at res < 22. It seems that it causes trouble when a MapLine that has the direction flag set is merged with another line. The flag is set if the OSM way is a oneway. I don't know why this is also done for non-routable ways, but that's how it is coded since 2008. Maybe Steve has an explanation? The attached small patch seems to fix the problem by excluding all oneways from merging, of course this makes the *.img a bit larger. I also tried to simply set the directionflag to false for all non-routable ways, but that did not help. Any idea would be welcome. excl_oneways_from_merging_v1.patch <http://gis.19327.n5.nabble.com/file/n5760488/excl_oneways_from_merging_v1.patch> A compiled binary is here: http://files.mkgmap.org.uk/download/122/mkgmap.jar Gerd Minko-2 wrote
Thanks, You can see this behaviour by editting the following line in the default style: #highway=trunk [0x02 road_class=4 road_speed=5 resolution 18] highway=trunk [0x02 resolution 18]
I think other mkgmap options don't matter but anyway here it is:
name-tag-list: name,int_name,name:en,name:nl,name:de,name:fr,place_name generate-sea: land-tag=natural=background precomp-sea: C:\Downloads\Sea\sea_20130415.zip bounds: c:\Downloads\Boundaries\bounds_20130420.zip location-autofill: is-in,nearest x-housenumbers tdbfile latin1 code-page: 1252 show-profiles: 1 ignore-maxspeeds add-pois-to-areas add-pois-to-lines preserve-element-order keep-going net route index
OK, thanks. I try to find out what happens.
Gerd
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/ways-are-deleted-when-not-routable-tp5760424p... Sent from the Mkgmap Development mailing list archive at Nabble.com.