You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the definition of a Geographic Coordinate Reference System is stored in an iModel using a semi-opaque binary structure. It should be instead stored as a JSON fragment for two reasons:
A - The JSON fragment is open and easily (so to speak) understandable by a human
B - The JSON fragments support definition details that are not supported by the binary structure (such as additional transforms) meaning people can create an iModel and try to set a GCRS that cannot be stored in the iModel.
Of course, support of the binary for reading is essential for older iModels.
The text was updated successfully, but these errors were encountered:
Currently the definition of a Geographic Coordinate Reference System is stored in an iModel using a semi-opaque binary structure. It should be instead stored as a JSON fragment for two reasons:
A - The JSON fragment is open and easily (so to speak) understandable by a human
B - The JSON fragments support definition details that are not supported by the binary structure (such as additional transforms) meaning people can create an iModel and try to set a GCRS that cannot be stored in the iModel.
Of course, support of the binary for reading is essential for older iModels.
The text was updated successfully, but these errors were encountered: