7.11.2016, 20:59, nwillink kirjoitti:
This is not a mkgmap error but clearly points to a type number Basecamp objects to.
Perhaps your 0x30 in lines?
-- View this message in context: http://gis.19327.n8.nabble.com/Spurious-points-Basecamp-blank-tiles-tp588543... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
0x30 types were problematic, but I tested that these artifacts are created without 0x30 lines. It looks like artifacts appear after I merge original OSM data to pbf files. Original custom pbf files converted from National Topographic Database GML has node/way/relations ids starting from 5000000000. Merged OSM data naturally has much smaller ids. I'm thinking this could have something to do with this problem. -Teemu