You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That behaviour is correct. The compression reported is the outside compression on something like .osm.bz2. The man page says:
File This section shows the information available without opening the file itself. It contains the file name, the format deduced from the file name, the compression used and the size of the file in bytes.
The compression inside the PBF blobs is not reported. This is because different blocks could be compressed differently. (I don't expect any software to actually do that, but it is possible.)
I see: the file section is not the correct section. The PBF compression could be included in the --extended output
...
Data:
Bounding box: (8.8331793,46.2012502,18.994394,49.3061616)
Timestamps:
First: 2005-07-28T14:53:13Z
Last: 2021-01-01T21:36:42Z
...
All objects have following metadata attributes: version+timestamp
Some objects have following metadata attributes: version+timestamp
+ All PBF data blocks use the compression: zlib
While I agree that this could be useful, it would need quite a lot of changes to libosmium and osmium-tool. The information is only available deep in side the library and there is no easy way to get it to the application. So this is unlikely to get implemented soon. I'll leave the issue open for the time being.
Currently, osmium-tool reports no compression, not taking into account whether a PBF blob has been compressed using zlib or lzma:
The text was updated successfully, but these errors were encountered: