opengeospatial / opengeospatial/CRS-JSON-Encoding
Definition of "defining_transformation" and "defining_transformations"
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.
"defining_transformation
"defining_transformations
"$comment": "[RL] definition of this association (attribute of a geodetic_crs, cardinality 0..*) is missing. Analogous to the geoid model association for vertical_crs. See comments under vertical_crs. Schema for both geoid model and defining transformation should be similar."
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 linked ProjJson v0-7 RL 2024-06-16.docx and compare the defining_transformation(s) request with the geoid model association for vertical_crs. Determine the intended definition, cardinality, and comparable schema shape before proposing a resolution. Done means the missing association is clearly specified and its schema treatment is agreed.
Written by the indexing model from the issue text.
Assessment
- 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