Discussion of bbox (bounding box)

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.

"bbox": {
"type": "object",
"properties": {
"east_longitude": { "type": "number" },
"west_longitude": { "type": "number" },
"south_latitude": { "type": "number" },
"north_latitude": { "type": "number" }
},
"required" : [ "east_longitude", "west_longitude",
"south_latitude", "north_latitude" ],
"additionalProperties": false
},

"$comment": "[RL] ISO 19115 has constraints on the bbox limits
-180 <= West Bounding Longitude Value <= 180
-180 <= East Bounding Longitude Value <= 180
-90 <= South Bounding Latitude Value <= 90; South Bounding Latitude Value <= North bounding Latitude Value
-90 <= North Bounding Latitude Value <= 90; North Bounding Latitude Value >= South Bounding Latitude Value
where the latitude and longitude must be in decimal degrees.
EPSG notes that when East Bounding Longitude Value > West Bounding Longitude Value (the usual case) the bbox does not cross the 180° meridian and when West Bounding Longitude Value > East Bounding Longitude Value the bbox crosses the 180° meridian."

Start with the quoted bbox schema in issue #6 and the linked ProjJson v0-7 RL 2024-06-16.docx document. Review the ISO 19115 and EPSG constraints described in the discussion; done requires a decided treatment of those constraints in the CRS JSON Encoding specification.