thanks, that patch fixed it... On 06.11.2012 19:53, GerdP wrote: > Hi Felix, > > > Felix Hartmann-2 wrote >> yes, I use 202 with boundingBox.patch - forgot to mention it (oh and >> hope it gets integrated into trunk soon..., I currently don't want to >> use the splitter branch...). > somehow the patch caused a bbox to be shifted to a value smaller than -180.0 > attached is a new version of the patch that makes sure that this doesn't > happen. > > boundingBox_v2.patch > <http://gis.19327.n5.nabble.com/file/n5734525/boundingBox_v2.patch> > > Gerd > > > > -- > View this message in context: > http://gis.19327.n5.nabble.com/mkgmap-splitter-error-java-lang-ArrayIndexOutOfBoundsException-DensityMap-subset-tp5734511p5734525.html > Sent from the Mkgmap Development mailing list archive at Nabble.com. > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
