We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@rms13
From the roadmap:
i3dm If NORMAL_UP/NORMAL_RIGHT (or NORMAL_UP_OCT32P/NORMAL_RIGHT_OCT32P) are defined, verify that they are orthonormal.
pnts If NORMAL/NORMAL_OCT16P are defined, verify they are of unit length.
Use the same Cesium3DTileFeatureTable object to extract the values. Look at https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Scene/Instanced3DModel3DTileContent.js#L363 for reading these values and converting the oct-encoded versions to regular numbers. (The OCT16P version will use a range of 255 instead of 65535 for octDecodeInRange)
Cesium3DTileFeatureTable
octDecodeInRange
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@rms13
From the roadmap:
Use the same
Cesium3DTileFeatureTable
object to extract the values. Look at https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Scene/Instanced3DModel3DTileContent.js#L363 for reading these values and converting the oct-encoded versions to regular numbers. (The OCT16P version will use a range of 255 instead of 65535 foroctDecodeInRange
)The text was updated successfully, but these errors were encountered: