opengeospatial / opengeospatial/ogcapi-features
Ability to set no null/empty geometry in returned response
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 386
- Forks
- 92
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 15
Description
Most of the data consumers from WFS need the geometry but sometimes, the service can provide data for charts or HTML tables where geometry would slow down the data retrieval due to geometry size in response.
I'm not sure if the specification implicitly manage this use case as I didn't found a way to do it from my understanding of the current Core spec.
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
Start by reading the OGC API Features Core specification and the WFS use case described in the issue. Determine whether the specification already supports omitting geometry for chart or HTML-table responses; done requires a decided, clearly defined specification change or confirmation that existing behavior is sufficient.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100