opengeospatial / opengeospatial/ogcapi-features
Fast access to feature count of a collection
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 386
- Forks
- 92
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 15
Description
There are some clients which could be made much faster if the return of the /collections/{collectionname} endpoint included the feature count, probably as an optional element. Like QGIS currently using the OGR WFS3 driver, and QGIS displays the list of all collections with their feature count, which causes currently at least an extra ?resultType=hits request to be issued.
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
Review the /collections/{collectionname} endpoint definition and the existing resultType=hits behavior. Compare how collection metadata and feature counts are represented, then determine the specification change needed for an optional count that avoids an extra request for clients such as QGIS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100