SQLite DB, ETL Tool and GeoJSON Generator #75
Conversation
This file contains hidden or 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
2 participants
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.
Took a stab at creating a SQLite database from the LTS data generated via @sckilcoyne's tool. I also created a python ETL tool,
database/load_into_sqlite.py, to take the CSV (and additional OSM Node data) and load it into a DB. For Boston, Cambridge, Somerville, Brookline, Chelsea, Everett, and Milton, the DB size is only 44mb, which about an order of magnitude smaller than the raw data. Plus, being able to query the data via SQL makes it really easy to interact with the data programmatically.To that point, I've created a little script at
geojson/geojson_from_ways.pythat leverages the new SQLite database. It can be used to create LTS-annotated GeoJSON for a JSON list of OSM Ways. It's really useful for route generation!