Switch the import process to use osm.pbf #1133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that osm2streets can read XML or PBF files without caring about the difference, the import pipeline here can be slimmed down to use the smaller (and faster tor read) PBF files. The
data/inputdirectory with all maps shrinks from 42GB to 34GB with this change.I regenerated everything on a laptop without Docker working properly, so the elevation data seems to have broken for Seattle. Uploading anyway. Working on a much simpler elevation reader without the same dependency problems in https://github.com/a-b-street/abstreet/tree/elevation and unlikely to do a new release anytime soon.