Re: [mkgmap-dev] New splitter build for pbf format
Hi Thats my fault. I didn't actually push the new osmpbf.jar to osmosis's SVN, so Steve never incorporated the latest, fixed, version of the jar. I've just pushed it so hopefully Steve can rerelease a new version. I apologize for the error. Ahh, so that was the bug in action. I've repackaged the splitter at URL: http://files.mkgmap.org.uk/download/8/splitter-r161-3.zip ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New splitter build for pbf format
Am 27.01.2011 03:55, schrieb Scott Crosby: The problem is entirely with the pbf reader --- a 32-bit cleanness bug that was only exposed on Windows made the reader erroneously sense end-of-file. Hi Scott, is this a known java Bug? If not, has it been reported to oracle ? Chris ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New splitter build for pbf format
Tested splitter-r161-3 on the latest europe.osm.pbf, it is working now, thanks! ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New splitter build for pbf format
On Thu, Jan 27, 2011 at 7:31 AM, Chris66 chris66...@gmx.de wrote: Am 27.01.2011 03:55, schrieb Scott Crosby: The problem is entirely with the pbf reader --- a 32-bit cleanness bug that was only exposed on Windows made the reader erroneously sense end-of-file. Hi Scott, is this a known java Bug? Don't know. You could argue that there's a 64-bit cleanliness issue in the API. InputStream.available() returns 32-bit integer. I was formerly calling that function to detect EOF, but its not needed if I instead catch EOFException. If not, has it been reported to oracle ? I've not reported it. Scott ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
