Hi Andrzej, yes, I did not test with your data yesterday and did not notice an old problem with high precision coordinates. Attached is a new patch that implements both changes which I suggested here: http://gis.19327.n5.nabble.com/Optimizing-MapSplitter-tp5823702p5824224.html I am not sure about the criteria. The line final int LARGE_OBJECT_DIM = 1024; gives a measurement for large objects in map units. Each large object is placed in its own sub div. The line int wantedSize = MAX_RGN_SIZE / 10; // smaller values result in more sub divs determines the approx. number of bytes in one sub div. A value near 0 means many very small sub divs, a value near MAX_RGN_SIZE is what the trunk version uses. Maybe we have to create parameters for them. Gerd
Date: Fri, 14 Nov 2014 22:54:38 +0100 From: popej@poczta.onet.pl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Optimizing MapSplitter
Hi Gerd,
your second patch doesn't work for me. When compiling I get multiple warnings like this: SEVERE (MapArea): 29483021.osm.pbf: Point with type 0x2d02 at http://www.openstreetmap.org/?mlat=54.594173&mlon=18.815332&zoom=17 is outside of the map area centred on http://www.openstreetmap.org/?mlat=54.509804&mlon=18.684912&zoom=17 width = 12155 height = 8502 resolution = 15
Img is much bigger, like 5MB instead of 3.8MB and I can't decompile it with GPSMapEdit. BaseCamp doesn't display it. I assume img is damaged.
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev