opengeospatial / opengeospatial/CRS-JSON-Encoding

Definition of "geoid_model"

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

"geoid_model": {
"type": "object",
"properties": {
"name": { "type": "string" },

"interpolation_crs": { "$ref": "#/definitions/crs" }, STRIKE THIS LINE
"transformation": { "$ref": "#/definitions/transformation" },

    "id": { "$ref": "#/definitions/id" }
  },
  "required" : [ "name" ],
  "additionalProperties": false
},

"$comment": "[RL] Is the geoid model(s) attribute correctly modelled? A geoid model is usually described as a transformation."

"$comment": "[RL] If its use in vertical_crs were changed as suggested below, is this geoid model member actually needed in the schema?"

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

Read the linked ProjJson v0-7 document and inspect the shown geoid_model definition, including the proposed removal of interpolation_crs and use of transformation. Resolve whether geoid_model is still needed in vertical_crs, then document the agreed schema decision and update the relevant validation coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
api
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.