Hi Thorsten, I think something must be wrong. I would not expect a change in file sizes and I did not see one in my test data. The patch verify_boundary_v3.patch doesn't remove any data, so I assume that you have applied one of the older patches. Can you please verify that ? The correct patch contains a line with Collections.reverse(coords); Gerd
Date: Sat, 11 Feb 2012 16:49:59 +0100 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] [PATCH] Again NullPointerException
Hi,
On Thu, Feb 09, GerdP wrote:
Hi,
as a result of previous discussions here is th new patch.
http://gis.19327.n5.nabble.com/file/n5471749/verify_boundary_v3.patch verify_boundary_v3.patch
With mkgmap-r2205, with and without this patch, I get an expecption on the planet data from 2012-02-10:
Exception in thread "main" java.lang.AssertionError at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadBoundaryFile(BoundaryUtil.java:145)
If I disable the assert, mkgmap-r2205 finishes building boundarys without problems.
There is only one big difference in the boundary data: The boundary data created by mkgmap with this patch is 15% smaller than the one created without this patch.
I don't know how to compare best which data is missing, but I think 15% is a lot. Or is this expected?
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev