I think this was discussed some time ago: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012193.html
WanMil > Hi Felix, > > >> Exact map coverage is (49.44551467895508,5.733017921447754) to >> (50.184946060180664,6.532230377197266) >> Trimmed and rounded map coverage is (49.482421875,5.712890625) to >> (50.185546875,6.50390625) > > I think the reason is that splitter writes a different bounding box to the > file. I am not sure, but it seems to be an error in RoundingUtils.java: > > int roundedMinLon = roundDown(b.getMinLong(), shift); > int roundedMaxLon = roundDown(b.getMaxLong(), shift); > > Both the min and the max value are rounded down. This looks wrong. > Similar problem with the latitude values: > int roundedMinLat = roundUp(minLat, shift); > int roundedMaxLat = roundUp(maxLat, shift); > > > Ciao, > Gerd > > > > > -- > View this message in context: > http://gis.19327.n5.nabble.com/mkgmap-splitter-or-mkgmap-leave-out-information-on-luxembourg-osm-pbf-from-geofabrik-tp5731208p5731274.html > 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 > _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev