opengeospatial / opengeospatial/CRS-JSON-Encoding
Definition of "spherical_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.
"spherical_cs": { }
"$comment": "[RL] Definition to be completed. The definition should constrain a spherical CS to have 2 or 3 axes.
When a spherical CS is used within a geodetic CRS, 19111/Topic2 constrains axis names (see Topic 2 Table 27). WKT2 requires that axis abbreviations be from the Latin character set and recommends that axis abbreviations φ and θ are be replaced by U and V."
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 with the “spherical_cs” fragment in the issue and the linked ProjJson v0-7 document. Check 19111/Topic2 Table 27 and the WKT2 axis-abbreviation guidance referenced there; the definition is done when it constrains spherical coordinate systems to two or three axes and documents the applicable naming rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100