add support for optional limit parameter for some query types #455
Labels
API EDR V1.2
Non-breaking change for Version 1.2
Comments
|
When the data response is in formats such as GeoJSON, I think it could also be useful for |
|
Addressed by PR #472 |
Closed
Merged
chris-little
moved this to In progress (Assignees working on it)
in OGC API-EDR Part 1: Core, V1.2 Backward compatible functional changes
chris-little
moved this from In progress (Assignees working on it)
to To do (SWG agreed to add to project)
in OGC API-EDR Part 1: Core, V1.2 Backward compatible functional changes
chris-little
moved this from To do (SWG agreed to add to project)
to Final Review (PR ready, no conflicts, reviewers requested)
in OGC API-EDR Part 1: Core, V1.2 Backward compatible functional changes
chris-little
moved this from Final Review (PR ready, no conflicts, reviewers requested)
to Initial Review (agreed as feasible, reasonable, achievable, and assigned)
in OGC API-EDR Part 1: Core, V1.2 Backward compatible functional changes
chris-little
moved this from Initial Review (agreed as feasible, reasonable, achievable, and assigned)
to Final Review (PR ready, no conflicts, reviewers requested)
in OGC API-EDR Part 1: Core, V1.2 Backward compatible functional changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For discrete data, It would be valuable for
.../radius,.../locations, and.../instancesquery types to support an optionallimitparameter as per OGC API - Features (note:limitis already supported (naturally) via the.../itemsquery type).The text was updated successfully, but these errors were encountered: