-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update reference feature contribution #177
Comments
I think the question is really, do we need to make any changes to things now because the current set up is problematic? I think leaving them in a single hydroshare resource out of convenience and starting to point to individual file artifacts seems reasonable. |
In light of cgs-earth/hydrodump-action, which downloads everyhting in hydroshare resource for this CI/CD, we can consolidate the update process to placing new files in the hydroshare resource and updating the pygeoapi config, with a comment about update time if all that's happening is updating a file |
Requires documentation published in github.com/internetofwater/reference.geoconnex.us |
The current CI/CD downloads everything (excepting specifically listed files) in the hydroshare resource https://www.hydroshare.org/resource/3295a17b4cc24d34bd6a5c5aaf753c50/ , then uses the github action to download them and convert them to tables within a PostGIS sql dump, which other CI/CD tools then use to update the production database.
We need to update both the process and guidance for reference feature contribution, since a Dockerfile no longer individually downloads gpkg files, whose names are automatically converted to postgres table names.
Theoretically, we can be agnostic to any OGR spatial data type, as long as
I think the first choices to be made philosophically are:
The text was updated successfully, but these errors were encountered: