stac-utils / stac-utils/stac-fastapi
PC advertises extensions for item-search but not ogcapi-features conformance classes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 324
- Forks
- 126
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Description
PC advertises:
"https://api.stacspec.org/v1.0.0-rc.1/item-search#fields",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#filter",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#filter:basic-cql",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#filter:cql-json",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#filter:cql-text",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#query",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#sort",
"https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features"
Which indicates that the extensions are only supported on the Item Search endpoints and not the Features /items.
I think all of those extensions are also supported on the Features endpoint, so they need to be advertised.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace how PC builds its advertised conformance classes for Item Search and Features /items endpoints. Compare the current Item Search extension declarations with the Features endpoint declarations, then verify that the supported extensions appear in the Features conformance response without removing their Item Search advertisements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100