Should the JSON encoding be a replacement for GML?

[desruisseaux]

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 (Definition of "bearing" (missing) #7).
• Coordinate system types polar, linear and cylindrical.
• GeographicCRS and DerivedGeographicCRS subtypes.
• All CoordinateSystem subtypes (currently represented by an enum in PROJJSON) (Definition of "coordinate system" #11).
• Domain (scope, description, bounding box, vertical/temporal extent) in conversions.
• Full operation definition in DeformationModel.
• GeodeticCRS.definingTransformation.
• OperationMethod.formula (Definition of "formula" (Missing) #29).
• Operation method parameters.
• realizationMethod on static and dynamic vertical CRS (Definition of "realization_method" (missing) #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.coordinateSystem should be restricted to TemporalCS.
• DerivedVerticalCRS.coordinateSystem should be restricted to VerticalCS.
• All other CRS types. See Should coordinate system subtypes be defined? #63 and Definition of "coordinate system" #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.