Problem with osmconvert pbf files

pbf files generated by osmconvert.exe appear to be incompatible with mkgmap.
Error at line 1, col 1 Bad file format: cumbria.pbf Error parsing file
Test sequence: 1. compile a pbf file generated by splitter - good 2. convert this file to osm with osmconvert.exe and compile - good 3. convert the osm file back to pbf with osmconvert.exe and compile - fails. Comparison of the 'before' and 'after' pbf files with a hex editor shows that they are very different (although they are the same at line 1 column 1). The 'after' file is about 230k smaller (in about 5M) than the 'before' file. I am using osmconvert version 0.7N and mkgmap 2353. Has anyone else encountered this problem? Roger -- ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------

Roger Calvert wrote
pbf files generated by osmconvert.exe appear to be incompatible with mkgmap.
Error at line 1, col 1 Bad file format: cumbria.pbf Error parsing file
Test sequence: 1. compile a pbf file generated by splitter - good 2. convert this file to osm with osmconvert.exe and compile - good 3. convert the osm file back to pbf with osmconvert.exe and compile - fails.
Comparison of the 'before' and 'after' pbf files with a hex editor shows that they are very different (although they are the same at line 1 column 1). The 'after' file is about 230k smaller (in about 5M) than the 'before' file.
I am using osmconvert version 0.7N and mkgmap 2353.
Has anyone else encountered this problem?
I can reproduce this problem with mkgmap when I rename a file from xyz.osm.pbf to xyz.pbf. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Problem-with-osmconvert-pbf-files-tp5742471p5... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Thanks all for identifying and fixing this so quickly. Roger On 03/01/2013 15:05, Steve Ratcliffe wrote:
Hi
I can reproduce this problem with mkgmap when I rename a file from xyz.osm.pbf to xyz.pbf. Yes files have to end in .osm.pbf ... thought we had fixed this already.
I will change this now, so that they only have to end with .pbf.
..Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- ------------------------------------------------------------------------ Roger Calvert Beckside House Blawith Ulverston LA12 8EQ 01229 885498 078 2746 8501 ------------------------------------------------------------------------

Roger Calvert wrote
Comparison of the 'before' and 'after' pbf files with a hex editor shows that they are very different (although they are the same at line 1 column 1). The 'after' file is about 230k smaller (in about 5M) than the 'before' file.
The different size is probably ok. The pbf format has a parameter that allows to set a "batchsize". This size influences the compression ratio. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Problem-with-osmconvert-pbf-files-tp5742471p5... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (3)
-
GerdP
-
Roger Calvert
-
Steve Ratcliffe