opengeospatial / opengeospatial/CRS-JSON-Encoding
Definition of temporalMeasure_cs" (missing)
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.
"temporalMeasure_cs": { }
"$comment": "[RL] Definition to be completed. The definition would constrain a temporalMeasure CS to have 1 axis and units to be real numbers."
"$comment": "[RL] Is use of upper camel case as member name ok?."
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
Start by reading the linked ProjJson v0-7 RL 2024-06-16.docx and the temporalMeasure_cs discussion in this issue. Determine the complete definition, including the one-axis and real-number unit constraints, and resolve whether the upper-camel-case member name is appropriate. Done means the definition and naming decision are recorded for the CRS SWG specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100