Open
Conversation
Author
|
For more information, these postgis tiger sql scripts come from here: https://postgis.net/docs/manual-3.6/en/Extras.html#Tiger_Geocoder |
Author
|
I'm pretty sure (but could be wrong) this simply need the user permissions fixed? And then the PG_USER in the python script adjusted. |
Author
|
This should now be ready for review and merging into main |
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
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.
This rework utilizes the postgis tiger geocoder extension built in
functions to load the data.
There is also the issue of the database user (which I removed and is currently
the default
postgresinstead of the previousclad_svcuser).