I’m in the process of implementing an instanced 3d tile. The model I have to display needs to be placed with double precision. I’ve successfully been able to use the POSITION attribute and simply add the coordinates in the JSON feature table definition, but I’ve been wondering if I could save up space by using the POSITION_QUANTIZED attribute instead.
These are some example coordinates (cartesian WGS84 X,Y,Z):
-157931.1604355328 -4381808.169387078 4616712.155528109
-157889.74656391866 -4381854.200775967 4616682.345822607
-157874.69581631612 -4381876.47130751 4616662.231937943
I’m not entirely sure what would be the right approach to implement this. I thought I could use QUANTIZED_VOLUME_OFFSET to define a center coordinate (similar to CESIUM_RTC?) but I noticed that the spec defines QUANTIZED_VOLUME_OFFSET as float32.
Am I just going to have to keep the positions in POSITION if I need double precision?