opengeospatial / opengeospatial/CRS-JSON-Encoding

Definition of "derived_projected_crs"

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

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.

"derived_projected_crs": {
  "type": "object",

"allOf": [{ "$ref": "#/definitions/object_usage" }],

  "properties": {
    "type": { "type": "string",
              "enum": ["DerivedProjectedCRS"] },
    "name": { "type": "string" },
    "base_crs": { "$ref": "#/definitions/projected_crs" },
    "conversion": { "$ref": "#/definitions/conversion" },
    "coordinate_system": { "$ref": "#/definitions/coordinate_system" },
    "coordinate_system": { "$ref": "#/definitions/derived_projected_cs" },
    "$schema" : {},

"scope": {},
"area": {},
"bbox": {},
"vertical_extent": {},
"temporal_extent": {},
"usages": {},

    "remarks": {},
    "id": {}, "ids": {}
 },
 "required" : [ "name", "base_crs", "conversion", "coordinate_system" ],
 "additionalProperties": false
},

"$comment": "[RL] See comment regarding usage under compound_crs."

"$comment": "[RL] A derived projected CRS should be constrained to having a derived_projected_cs." defined as follows

"derived_projected_cs": {
  "type": "object",
  "properties": {
       "oneOf": [
            { "$ref": "#/definitions/affine_cs" },
            { "$ref": "#/definitions/Cartesian_cs" }
            { "$ref": "#/definitions/cylindrical_cs" }
            { "$ref": "#/definitions/ordinal_cs" }
            { "$ref": "#/definitions/polar_cs" }
            { "$ref": "#/definitions/spherical_cs" }
       ]
  "additionalProperties": false
},

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked ProjJson v0-7 document and compare its proposed derived_projected_crs and derived_projected_cs definitions with the repository's current schema. Review the CRS SWG discussion context, including the duplicate coordinate_system entries and usage properties, then confirm the intended definition and constraints before updating the schema. Done means the group has an agreed, internally consistent definition.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.