-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PBF error: illegal blob size #275
Comments
I can not reproduce this. I used the USA file from Geofabrik and did the steps you describe and the resulting file is fine. I had to repair the config file you provided, it does not work otherwise. Are you sure the The other thing: The Delaware.osm.pbf you seem to have is rather large, 650 MB. Mine is only 19 MB. |
The input PBF file that I have for USA is indeed enriched with other data sources. That's why it's bigger. Would it be ok for you if I upload a piece of USA that I'm working with somewhere, and send it to you to reproduce the issue? Shall I send the link privately to jochen@topf.org ? Otherwise I'd violate my company's data privacy. Also what was the repair that you did on the config file?
Yes, I'm pretty sure that |
Ah, you should have mentioned that you are working with proprietary data. If you want support for that, please contact me by email and I'll send you my consulting rates. |
@joto thank you for your answer.
Ok. If we decide that we definitely must send our propriety data to you, I'll hand-over your consulting fee to my manager. My suspicion is about In this line In other words, we don't check the size() + sizeOfEntityToBeAdded < max_used_blob_size. Is my understanding correct from the |
Side note: as workaround, I changed the max_entities_per_block to 1000 (instead of the default 8000), compiled the osmium + libosmium, and now the PBFs that Would you agree that this is a signal that the |
What version of osmium-tool are you using?
What operating system version are you using?
Tell us something about your system
What did you do exactly?
My intention is to extract Delaware out of USA. These are the steps that I take to achieve this:
osmium tags-filter --output USA.boundary.pbf --overwrite --no-progress USA.osm.pbf r/ISO3166-1:alpha3=USA
osmium tags-filter --output US-DE.boundary.pbf --overwrite --no-progress USA.boundary.pbf r/ISO3166-2=US-DE
osmium extract --config config.json --option complete-partial-relations=65 --strategy smart --verbose --overwrite --no-progress USA.osm.pbf
These commands go through successfully and create the intended Delaware file, but the Delaware file seems to be corrupted. When I run
osmium fileinfo -e Delaware.osm.pbf
, it crashes showing the following error:What did you expect to happen?
Running
osmium fileinfo -e Delaware.osm.pbf
should not crash sayingPBF error: illegal blob size
.What did you do to try analyzing the problem?
At the beginning I suspected that the input data is corrupted, so I executed the following commands on USA.osm.pbf:
osmium fileinfo -e USA.osm.pbf
osmium check-refs USA.osm.pbf
Both of the above command properly show the statistics, and report that there is no referential integrity issues. Also, it is noteworthy to mention that I am able to cut all the other US states, and all of them pass fileinfo and check-refs commands.
To summarize, my input pbf is valid (because of the two above commands), but after extract the output pbf becomes corrupted (because it cannot complete any of the above commands). Given the described situation, would you agree that there might be an issue in the osmium tool? Do you need me to send you some pieces of the data?
The text was updated successfully, but these errors were encountered: