opengeospatial / opengeospatial/CRS-JSON-Encoding
Should coordinate system subtypes be defined?
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 3
Description
Issues #4, #8, #13, #33, #42 and #46 have the same root and could be merged in a single issue here: the subtype element in PROJJSON does not refer to a class type. This is probably the reason why its name is not type like in other elements. Instead, subtype refers to an enumeration value similar to the value of the CS["foo"] element in WKT. That is why there is no CoordinateSystem subtype, and why all coordinate_system elements in PROJJSON refers to "#/definitions/coordinate_system" instead of a more specific subtype.
So a question is: should it be converted to the class hierarchy as defined in ISO 19111, and as used everywhere else in PROJJSON (e.g. for datum)?
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 by reviewing the subtype element, the coordinate_system elements, and #/definitions/coordinate_system in the PROJJSON encoding, then compare their meaning with ISO 19111 and WKT CS["foo"]. Done means deciding whether coordinate-system subtypes should follow the ISO 19111 class hierarchy and resolving the related issues (#4, #8, #13, #33, #42, and #46).
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
- 25/100