opengeospatial / opengeospatial/CRS-JSON-Encoding
Definition of "method"
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.
"method": {
"type": "object",
"properties": {
"$schema" : { "type": "string" },
"type": { "type": "string", "enum": ["OperationMethod"]},
"name": { "type": "string" },
"formula": { "type": ""#/definitions/formula" },
"id": { "$ref": "#/definitions/id" },
"ids": { "$ref": "#/definitions/ids" }
},
"required" : [ "name" ],
"allOf": [
{ "$ref": "#/definitions/id_ids_mutually_exclusive" }
],
"additionalProperties": false
},
"$comment": "[RL] In 19111/Topic 2, operation method requires one of a formula or a formula citation. In WKT2 for reasons of brevity it was decided to rely on an identifier (authority reference) to a method in a registry such as EPSG, although this is optional. If CRS JSON is to be capable of carrying the full definition of a coordinate operation (transformation, conversion or point motion operation) then method will need to require one of ID, formula or formula citation."
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
Read the referenced ProjJson v0-7 RL 2024-06-16.docx and compare its proposed method schema with the current CRS JSON Encoding specification. Resolve whether formula, formula citation, or an identifier should be required, then update the specification once the CRS SWG agrees on the definition.
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