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
What is the precedence of scaling/offset information: shall we trust whatever is written in the LAS/LAZ file (and ignore ept.json) or prefer what is stored in ept.json?
A related question is whether ept.json should report X/Y/Z as doubles or as ints (given that's how they are actually stored in LAZ)
The text was updated successfully, but these errors were encountered:
Scale/offset applies to XYZ as well, otherwise binary/zstandard/other future generic encodings would not work. LAZ, although the default due to its compression ratio, is kind of the odd one out in that it is re-specified in the encoding itself.
So for LAZ data, the schema should show the scale/offset and advertise their values as int32 values.
In EPT decoder we read offset+scale from ept.json, but
bu
does not write scaling information to the ept.json:When I edited the ept.json to include scaling, the decoder/renderer started to work:
What is the precedence of scaling/offset information: shall we trust whatever is written in the LAS/LAZ file (and ignore ept.json) or prefer what is stored in ept.json?
A related question is whether ept.json should report X/Y/Z as doubles or as ints (given that's how they are actually stored in LAZ)
The text was updated successfully, but these errors were encountered: