Database #37
Closed
Database #37
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
|
I'm an idiot and pushed this all to master. |
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.
In order to allow for more dynamic queries we needed to move away from the overpass API, this PR adds a Postgres database that is populated with UVIC's OpenStreetMap data using osm2pgsql.
This has an added complexity cost as the project is now considerably more difficult to build - docker is more or less a necessity. I've updated the documentation to hopefully alleviate this.
The main actual code change is removing the network-based overpass queries and their respective caches and replacing it with a database-based data provider. I also reworked how to swagger component naming is generated in order to avoid naming conflicts. (which is why this PR seems to touch a million files).
Resolves #29