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
It looks like the osmium extract step is not producing a usable OSM.PBF file that can be used in the last step to generate the task files for Baltimore. The extract step completes the process without error. Yet, the file that was produced was suspiciously small, and did not load data into QGIS--attributes all appear NULL. I have confirmed that the original OSM.PBF file, downloaded from geofabrik, for the state of Maryland has no issues.
The files below include the original Maryland OSM.PBF data, the baltimore_johnsHopkins.geojson file that was extracted from geojson.io. Both files were verified in QGIS. The trimmed file that was generated in the extract step is named baltimore-jh-error.osm.pbf.
The file set has been included in a zip file that can be downloaded here: [https://drive.google.com/file/d/1fGWq977ghOOtf9_ghrzlshKY_79jFAKq/view?usp=share_link]
The text was updated successfully, but these errors were encountered:
It looks like the osmium extract step is not producing a usable OSM.PBF file that can be used in the last step to generate the task files for Baltimore. The extract step completes the process without error. Yet, the file that was produced was suspiciously small, and did not load data into QGIS--attributes all appear NULL. I have confirmed that the original OSM.PBF file, downloaded from geofabrik, for the state of Maryland has no issues.
The files below include the original Maryland OSM.PBF data, the baltimore_johnsHopkins.geojson file that was extracted from geojson.io. Both files were verified in QGIS. The trimmed file that was generated in the extract step is named baltimore-jh-error.osm.pbf.
The file set has been included in a zip file that can be downloaded here: [https://drive.google.com/file/d/1fGWq977ghOOtf9_ghrzlshKY_79jFAKq/view?usp=share_link]
The text was updated successfully, but these errors were encountered: