opengeospatial / opengeospatial/CRS-JSON-Encoding

Definition of "CRS"

Open
#12 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.

"crs": {
  "oneOf": [
    { "$ref": "#/definitions/bound_crs" },
    { "$ref": "#/definitions/compound_crs" },
    { "$ref": "#/definitions/derived_engineering_crs" },
    { "$ref": "#/definitions/derived_geodetic_crs" },

{ "$ref": "#/definitions/derived_geographic_crs" },

    { "$ref": "#/definitions/derived_parametric_crs" },
    { "$ref": "#/definitions/derived_projected_crs" },
    { "$ref": "#/definitions/derived_temporal_crs" },
    { "$ref": "#/definitions/derived_vertical_crs" },
    { "$ref": "#/definitions/engineering_crs" },
    { "$ref": "#/definitions/geodetic_crs" },

{ "$ref": "#/definitions/geographic_crs" },

    { "$ref": "#/definitions/parametric_crs" },
    { "$ref": "#/definitions/projected_crs" },
    { "$ref": "#/definitions/temporal_crs" },
    { "$ref": "#/definitions/vertical_crs" }
  ]
},

"$comment": "[RL] 2x CRS subtypes possibly missing?? See comment under geodetic_crs."

"$comment": "[RL] the concept of bound_crs is not recognised in Topic 2 (18-005r8) but it is defined in CRS WKT (18-010r11)(for backward compatibility of WKT2 with some flavors of WKT1). Should it (and abridged_transformation) be included in CRS JSON?"

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 the crs definition's oneOf list. Compare the missing CRS subtypes and the questions about bound_crs and abridged_transformation with the cited Topic 2 and CRS WKT specifications; done requires an agreed decision on the schema contents.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.