The second question I have is about the "precision" attribute, that, as
far as I understood, allows to define the resolution of a field only as
a multiple/submultiple of 10 - is that correct?
In some of our use cases it would be useful to define a different
resolution, for instance 0.5 m for a depth, or pi/180 for an angle in
radians. Restricting the resolution to multiples of 10 results in some
waste of space, especially when the field is "repeated".
Do you think it would make sense to add support for a "resolution"
attribute (mutually exclusive with "precision" to preserve backward
compatibility) that allows to specify the field's resolution as a real
number (or a Lua expression)?
On 9/21/22 19:57, Fenucci, Davide wrote: