opengeospatial / opengeospatial/Geospatial-User-Feedback
How to use OGC API records as a base for OGC API GUF
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Our OGC API GUF will specify a set of conformance classes that will be referenced in the conformsTo member for the collection of for individual records. See: https://github.com/opengeospatial/ogcapi-records/issues/215 and https://github.com/opengeospatial/ogcapi-records/issues/229 and the actual draft specification: http://docs.ogc.org/DRAFTS/20-004.html
Contributor guide
No contributing guide indexed for this repository
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
Read the linked OGC API Records issues 215 and 229, then compare their guidance with the draft specification at docs.ogc.org/DRAFTS/20-004.html. Done means documenting an agreed approach for using OGC API Records as the basis for OGC API GUF and specifying the relevant conformance-class references.
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
- 20/100