Actually the way I put the rounding now (to include everything) - is the way it has been up to rev 104, then came rev105 and the change (28.1.2010) - the patch did the same thing as I did. However actually now that I think about it - I can only come up with one explication why rev 105 on splitter was done - that is so that tiles don't overlap. Because the current hack means all tiles will be expanded. What we really need is to have the splitter identify ALL outside edges. Only on outside edges it shall do as I wrote lower down, on edges to the inside rev 105 is the way to go. So can anyone code that in? On 17.10.2012 20:23, WanMil wrote:
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-informati... 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
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org