sampleHeightMostDetailed is too slow when the 3dtile have many levels
Open
category - 3d tiles
type - enhancement
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
I suggest that we have the freedom to choose the level we want to calculate to, rather than the most detailed level.
Contributor guide
Research direction
The issue names the sampleHeightMostDetailed entry point but no file or test. Start by locating that entry point and tracing how the 3D Tiles level is selected. Done means callers can choose the calculation level instead of always requiring the most detailed level, with the behavior covered by the relevant existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100