opengeospatial / opengeospatial/bblocks
Add OGC API Records base building block
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
OGC API records schema is here: https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/schemas/recordGeoJSON.yaml
Building block should be just schema for now.
Need to check duplication of core components and refactor to use existing building blocks.
Extensions for profiles such as STAC will follow.
GeoDCAT-records will extend and map to the GeoDCAT ontology as it emerges here: https://github.com/ogcincubator/geodcat-ogcapi-records
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 Records recordGeoJSON.yaml schema linked in the issue, then inspect existing building blocks for duplicate core components. The work is done when the base OGC API Records schema exists as a building block and reused components are refactored rather than duplicated; profile extensions are out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, yaml
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100