Definition of "derived_engineering_crs"

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.

"derived_engineering_crs": {
  "type": "object",
  "allOf": [{ "$ref": "#/definitions/object_usage" }],
  "properties": {
    "type": { "type": "string",
              "enum": ["DerivedEngineeringCRS"] },
    "name": { "type": "string" },
    "base_crs": { "$ref": "#/definitions/engineering_crs" },
    "conversion": { "$ref": "#/definitions/conversion" },
    "coordinate_system": { "$ref": "#/definitions/coordinate_system" },
    "coordinate_system": { "$ref": "#/definitions/engineering_cs" },
    "$schema" : {},
    "scope": {},
    "area": {},
    "bbox": {},
    "vertical_extent": {},
    "temporal_extent": {},
    "usages": {},
    "remarks": {},
    "id": {}, "ids": {}
 },
 "required" : [ "name", "base_crs", "conversion", "coordinate_system" ],
 "additionalProperties": false
},

"$comment": "[RL] See comment regarding usage under compound_crs."
"$comment": "[RL] An engineering CRS should be constrained to having an engineering_cs."

The payload names no repository files or tests; start with the quoted derived_engineering_crs schema and the linked ProjJson v0-7 document. Compare the duplicate coordinate_system entries and the engineering_cs constraint, then confirm the agreed schema and required properties as done.