-
Notifications
You must be signed in to change notification settings - Fork 3.7k
3d tiles terrain #12963
New issue
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
base: main
Are you sure you want to change the base?
3d tiles terrain #12963
Conversation
…ior that resolves values immediately
3D Tiles terrain water mask
Thank you for the pull request, @jjhembd! ✅ We can confirm we have a CLA on file for you. |
}); | ||
|
||
if (!defined(bufferLoader)) { | ||
bufferLoader = resourceCache.addBufferLoader({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both resourceCache.getEmbeddedBufferLoader
and .addBufferLoader
call ResourceCacheKey.getEmbeddedBufferCacheKey
, which involves expensive URI parsing. For other 3D Tilesets, we have previously found that URI parsing can be a bottleneck.
We may want to consider reverting to the old getEmbeddedBufferLoader
syntax, which re-used the key.
Description
TODO
See restrictions on the structure of 3D Tiles data to be used as terrain: #12296 (comment)
Issue number and link
Resolves #12296
Testing plan
TODO before moving this out of "Draft":
Check
calls:EllipsoidalOccluder
,GoogleEarthEnterpriseTerrainData
,TerrainEncoding
(separate from other changes in file),binarySearch
,mergeSort
,QuantizedMeshTerrainDataSpec
. Beware incorrect capitalizations like{Object}
,{Number[]}
! See Clean up docs and type checks for terrain providers #12969ResourceCache
. The newgetEmbeddedBufferLoader
->addBufferLoader
sequence involves additional URI parsing, which has performance implications.TerrainEncoding
Author checklist
CONTRIBUTORS.md
CHANGES.md
with a short summary of my change