CRS for GeoJSON encoding for GeoSciML 4.2

[nmtoken]

Re proposal: the CRS attribute (that was introduced in GJ2008 and then removed should be implemented as a profile)

Do nothing and feed into /adopt OGC Features and Geometries JSON

ref: https://portal.ogc.org/files/95319?utm_source=phplist780&utm_medium=email&utm_content=HTML&utm_campaign=OGC+Members+propose+new+Features+and+Geometries+JSON+Standards+Working+Group%3B+public+comment+sought

[nmtoken]

Latest draft ~ https://github.com/opengeospatial/ogc-feat-geo-json/releases/tag/v0.3.0

https://docs.ogc.org/DRAFTS/21-045.html#place

[nmtoken]

Related to https://github.com/opengeospatial/GeoSciML/tree/master/geojson#geometry-property

Geometry property
GeoSciML lite expects the geometry to be in a field called "shape", but GeoJSON already imposes "geometry". Spatial query would technically target a different field depending of the encoding, but the spatial field is often "implicit" as the basic GML Level 0 model assume there is one and only on geometry per feature.

JSON-FG has either/or (in fact both are allowed) of geometry and place see: opengeospatial/ogcapi-features#1019 (comment) for recent discussion on this.

See also https://docs.ogc.org/bp/24-017r1.html#jsonschema_req_jsonfg_primary_geometry (Best Practice for OGC - UML to JSON Encoding Rules)

To me (to allow for all CRS) would mean mapping shape as the primary geometry to JSON-FG place