Load parcels from SQL database rather than from shapefiles#107
Merged
Load parcels from SQL database rather than from shapefiles#107
Conversation
…l data stored on a database rather than a shapefile
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
1 participant
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.
Building parcels to run WOFOST required querying a shapefile containing spatial information about all parcels in the UK. This was clunky and time consuming, as well as inefficient for data storage. Now the parcel data has been moved into a postgreSQL-postGIS database with indexing on parcel IDs which makes it much more efficient. Parcel data is stored in the same database where the elevation data is contained, which needs to be specified in the 'config.ini' file created from the
config.ini.exampletemplate configuration file.