opengeospatial / opengeospatial/CRS-JSON-Encoding
Definition of "temporal_extent"
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 3
Description
NOTE: Markdown does not support highlighting in color, so bold/italic has been used to highlight the material being discussed. This issue is extracted from the document submitted by Roger Lott at https://github.com/opengeospatial/CRS-JSON-Encoding/blob/main/ProjJson%20v0-7%20RL%202024-06-16.docx for discussion at the CRS SWG meeting OGC held during the Montreal June 2024 TC meeting.
"temporal_extent": {
"type": "object",
"properties": {
"start": { "type": "string" },
"end": { "type": "string" }
},
"required" : [ "start", "end" ],
"additionalProperties": false
},
"$comment": "[RL] If both start and end are required, how does one express a continuing time period e.g. 'after start = t' or 'before end = t' ?"
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 temporal_extent schema in issue #49 and the linked ProjJson v0-7 RL 2024-06-16.docx first. Resolve how open-ended periods should be represented, then record the agreed definition and update the schema requirements accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100