There appears to be a 32-bit problem with java on Windows where the java runtime reports a spurious end-of-file indication to the reader, which then assumes the file has been completely read. This occurs even with 64-bit Java on 64-bit windows. In your particular case, it believes the file ends at offset 10820815244-2*(2**32) or at around offset 2,230,000,000
I have an idea of a workaround but have not implemented it and do not have a windows box to test it on. Scott On Tue, Jan 4, 2011 at 2:35 AM, Stephan Knauss <[email protected]> wrote: > Hi, > > I tried osmosis together with PFB > > Did I specify some parameters wrong or is there a problem with PBF? > > Windows x64, Java x64 > > ..\osmosis-r24958\bin\osmosis.bat --read-xml-change > file=20110102-20110103.osc.gz --buffer-change bufferCapacity=1000 --read-pbf > file=planet-20110102.pbf --buffer bufferCapacity=1000 --apply-change > --buffer bufferCapacity=1000 --write-pbf file=planet-20110103.pbf > > The resulting PBF looks a bit small, but no errors on the console besides > others than this warning (which seams to be normal): > Attention: Data being output lacks metadata. Please use omitmetadata=true > > ----------+ 1 Stephan None 10820815244 2011-01-04 00:17 planet-20110102.pbf > ----------+ 1 Stephan None 2262773983 2011-01-04 03:14 planet-20110103.pbf > > Stephan > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev > _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
