Review the coordinate-axis contract behind Iceberg default CRS compatibility
Evaluate a default CRS and table CRS through the file format's coordinate order and a reviewed pair, rather than names alone. A documented compatibility convention does not establish interchangeability for every CRS.
Exchange meaning precedes name changes
CRS compatibility should follow an explicit coordinate-axis contract rather than name substitution alone. Truthound Core can check a prepared approval table after the operator reviews the writer and reader’s geospatial meaning. [1, 2, 3]
Default CRS and EPSG:4326
Iceberg issue #18680 reports Arrow-written default CRS being read as ogc:crs84 and rejected against EPSG:4326 geometry or geography on main. Follow-up discussion explains the conventional longitude-latitude axis policy codified in Parquet and recommends compatible handling for this pair; it is not a universal CRS-equivalence rule. [1]
Record axis convention
Record writer, stored/default CRS, interpreted CRS, table CRS, and axis policy. Use that information to approve the actual exchange pair. Preserve the distinction between official CRS axis definitions and the file format’s specified coordinate order. [1, 3]
Approve reviewed pairs only
The illustrative approval flag is true only for a writer-reader pair whose axis meaning has been reviewed independently. true passes that approval condition; false fails and blocks a forced alias change. A plausible map alone is not the reference. [1, 3]
Geospatial meaning stays external
ColumnPairValidator in Truthound Core Python SDK 3.3.2 can compare the prepared non-null reviewed-pair flag with its approved state. The SDK does not parse PROJJSON, reproject coordinates, or guarantee geographic accuracy. Those semantics must be supplied by the operator. [1, 2, 3]
Use known coordinates
Use a supported writer configuration with explicit axes and known reference coordinates. Follow the relevant Parquet convention when reviewing EPSG:4326 and OGC:CRS84 rather than extending the same decision to unrelated CRS pairs. [1, 3]
Preserve the accepted convention
The field names may be compatible under a specific exchange convention while still needing careful documentation. Retaining that convention makes the acceptance decision reproducible across language implementations. [1, 3]
Application conditions
Prepare writer/CRS interpretation, table CRS, and the approved coordinate-axis convention.
Alternatives
Check exchange with an explicit-axis supported writer and known reference coordinates.
Limitations
Do not extend this pair’s compatibility discussion to every CRS name.
Evidence
- Event checked
- Subject checked
- Modified
