File format

[kpetrow]

Hi,
I am looking into using the OMF format for data exchange. Is this format really in JSON utf-8? How does it handle large surface data? I am currently using a compressed Uint16 in binary format and struggle to open large terrain models. Has this format been stress tested and what are the limitations?

https://omf.readthedocs.io/en/stable/content/io.html

Following the binary is a UTF-8 encoded JSON dictionary containing all elements

[timmclennan]

Hey,

Note: I'm currently not involved in this project, but have been in the past so can answer this question,

Your quoted comment actually contains the important detail.

Following the binary is a UTF-8 encoded JSON dictionary containing all elements

In v1, the numeric arrays for the data (so vertex location and triangle indices for meshes) are stored as binary data with the JSON section containing meta data to interpret those arrays.

This has been revised for v2 which is under development at present, but it should still be stored relatively efficiently.

Still if you're looking at just storing large terrain models with a particular structure, there are likely other formats more optimised for your use.