Repository navigation
fix(core/pygeoapi): add feature provider to Water Chemistry & Water Levels (BDMS-1536) - #1046
Open
TylerAdamMartinez wants to merge 2 commits into
Conversation
Contributor
Coverage✅ 81.76% total — gate is 75%. Coverage for the Python files changed in this PR
|
This branch has not been deployed
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.
Why
This PR addresses the following problem / context:
/ogcapi-internal/collections/{collection}/itemsendpoint requires a feature provider, but Water Chemistry and Water Levels previously registered only EDR providers./itemsresponse to generate CSV downloads.How
Implementation summary: the following was changed / added / removed:
DescribedPostgreSQLProviderto construct GeoJSON point geometries from longitude and latitude fields when no geometry column exists.Author Checklist
Changes are limited to the intended scope.No secrets, credentials, or sensitive data were publicly exposed.Documentation was updated where necessary.Reviewer Checklist
Notes
Any special considerations, known limitations, risks, workarounds, or follow-up work to note?