OGC API #382
Merged
OGC API #382
Conversation
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
…m retrieval Issue #333
jirhiker
requested review from
TylerAdamMartinez,
chasetmartin,
Copilot,
kbighorse and
ksmuczynski
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds OGC API - Features support to expose well data through standardized geospatial endpoints, including well purposes, casing materials, and screen information, with property filtering capabilities for relationship-backed fields.
Changes:
- Added OGC API - Features endpoints (
/ogc) with support for wells, springs, and locations collections - Implemented property filtering for relationship-backed fields (well_purposes, well_casing_materials, well_screen_type) using EXISTS subqueries
- Added comprehensive test coverage for OGC endpoints and filtering capabilities
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| tests/test_ogc.py | New test file with comprehensive OGC API endpoint tests including landing page, conformance, collections, and various filtering scenarios |
| tests/conftest.py | Added database permissions setup for app_read role to support OGC queries |
| core/initializers.py | Registered the new OGC router in the application |
| api/ogc/schemas.py | Defined Pydantic schemas for OGC API responses including collections, features, and conformance |
| api/ogc/router.py | Implemented OGC API router with endpoints for landing page, conformance, collections, and feature items |
| api/ogc/features.py | Core feature query logic with support for bbox, datetime, property, and CQL filters |
| api/ogc/conformance.py | Declared conformance classes for OGC API - Features and CQL2 text support |
| api/ogc/collections.py | Collection metadata and link generation for locations, wells, and springs |
| api/ogc/init.py | Package initialization file |
| README.md | Added documentation and usage examples for OGC API endpoints and filtering options |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 973a1099eb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…d enhance clause splitting logic
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:
How
Implementation summary - the following was changed / added / removed:
Notes
Any special considerations, workarounds, or follow-up work to note?