Store longitude and latitude in degrees instead of radians

[lilleyse]

For the next version of 3D Tiles we should consider using degrees instead of radians for longitude and latitude values. Right now this only applies to the region bounding volume. Its CRS is EPSG:4979, which is in degrees, but its values are stored in radians. It will be easier for 3D Tiles to interoperate with other GIS formats if we make the switch to degrees.

Current

"boundingVolume": {
  "region": [
    -1.5707963267948966,
    -3.1415926535897932,
    1.5707963267948966,
    3.1415926535897932,
    -11.89207010413975,
    547.7591827297583
  ]
}

Proposed

"boundingVolume": {
  "region": [
    -90,
    -180,
    90,
    180,
    -11.89207010413975,
    547.7591827297583
  ]
},

[karlengstrom]

Yes!

Perhaps,

90, -180
-90, 180

[lilleyse]

See similar discussion in EXT_geopose_basic_euler

• Radians is consistent with 3D Tiles and glTF units: All angles are in radians
• Degrees is consistent with EPSG:4979

Which consistency matters more? While keeping in mind that switching to degrees would be a breaking change.