Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • What is the data format after step 1 in your pipeline? If you have the raw coodinates there it would be possible to just extract the min and max values per feature and be done. Commented Nov 22, 2020 at 13:00
  • @bugmenot123 osmium generally filters out to another (smaller) PBF file. But even after exporting to gpkg, parsing the file to extract the bounds, while not extraordinarily difficult, is not something I'd want to do by hand… Commented Nov 22, 2020 at 13:50
  • I'd pipe the osmium_extract into osmium_export with boudary filter and import into PostgreSQL (you can get a GeoJSON, too); I know you explicitly want to use no intermediate storage, but its trivial to go from there. Commented Nov 22, 2020 at 14:26
  • @geozelot intermediate storage isn't a big deal (though having to write/load/parse large files might be), but unless I'm missing something, the boundary filter on osmium_export will not result in a file that contains bounding boxes of the original polygons… Commented Nov 22, 2020 at 14:33
  • duplicate of : stackoverflow.com/questions/44975952/… ? Commented Nov 23, 2020 at 15:19