opengeospatial / opengeospatial/CRS-JSON-Encoding
Should the JSON encoding be a replacement for GML?
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Makefile
- Sterne
- 0
- Forks
- 2
- Ø Merge
- 1 Std. 36 Min.
- Gemergte PRs (30 T.)
- 3
Beschreibung
An open question is whether a CRS JSON encoding could be a replacement for GML. GML is currently the only encoding capable to represent fully the ISO 19111 model, but is based on the 2007 version of ISO 19111 with no plan yet to upgrade to latest ISO 19111 revision. One possibility would be to replace GML by JSON, in which case PROJJSON would need to be completed with the ISO 19111 elements that are currently missing. Those additions can probably be done in a compatible way. Whether the JSON encoding should be restructured (elements renamed or moved in an incompatible way) is not the topic of this issue.
Alternative
An alternative is to keep PROJJSON as it currently is, and instead restart the GML effort with a reduced scope. The parts of the GML schema that are about CRS definitions could be extracted and updated without the rest of GML. The update could use as a starting point the extensions that EPSG made for representing the new ISO 19111 data structures in the EPSG registry. This alternative has not been debated yet.
Missing elements
The following list is derived from the ProjJson v0-7 RL 2024-06-16.docx document. It may contain errors from my transcription from the document, and some elements may have been forgotten:
- Aliases in all objects.
CoordinateSystemAxis.bearing(#7).- Coordinate system types
polar,linearandcylindrical. GeographicCRSandDerivedGeographicCRSsubtypes.- All
CoordinateSystemsubtypes (currently represented by an enum in PROJJSON) (#11). - Domain (scope, description, bounding box, vertical/temporal extent) in conversions.
- Full operation definition in
DeformationModel. GeodeticCRS.definingTransformation.OperationMethod.formula(#29).- Operation method parameters.
realizationMethodon static and dynamic vertical CRS (#45).
Missing constraints
Many constraints cannot be enforced in a JSON schema and need to be stated in the text. However, the following elements may be made more specific:
DerivedTemporalCRS.coordinateSystemshould be restricted toTemporalCS.DerivedVerticalCRS.coordinateSystemshould be restricted toVerticalCS.- All other CRS types. See #63 and #11 for a more general discussion.
Missing features
GML can reference an external document using xlink. This feature is important for making possible to define an operation method once, then reuse it in many CRS definitions. There is currently no equivalent features in PROJJSON.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginnen Sie mit dem Dokument ProjJson v0-7 RL 2024-06-16.docx und den aufgeführten PROJJSON-Lücken, und vergleichen Sie sie anschließend mit dem aktuellen Umfang von GML und ISO 19111, der im Issue beschrieben ist. Prüfen Sie die beiden Alternativen, einschließlich der Wiederverwendung von xlink und der fehlenden Einschränkungen. Als abgeschlossen gilt die Dokumentation einer klaren Entscheidung darüber, ob PROJJSON GML ersetzt oder die GML-Arbeit mit reduziertem Umfang neu gestartet wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- json, xml
- Bereich
- backend-api-design
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100