opengeospatial / opengeospatial/ogcapi-features
Features API needs a zoom parameter
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 386
- Forks
- 92
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 15
Description
One of the major historical problems with WFS has been the lack of a standard approach to enabling different resolutions of feature geometry, or indeed different geometry types, based on the user's need.
I believe that the lack of a zoom level parameter in the new OGC features API is a major omission, and makes the proposed specification not only incompatible with the Spatial Data on the Web Best Practices:
This OGC standard is consistent with the OGC/W3C Spatial Data on the Web Best Practices.
but more importantly, with Web mapping in general.
Here are some relevant passages from the SDW-BP and here and here and probably others.
Please consider, at a minimum, adding a recommended zoom parameter.
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 current OGC API Features specification alongside the linked Spatial Data on the Web Best Practices passages. Determine whether a recommended zoom parameter should be added for geometry resolution or type selection, and document the specification decision and resulting wording as the definition of done.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100