Better viewer.zoomTo/flyTo for data sources
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
Right now, zooming to an entire data source uses the currently computed bounding sphere of all entities inside of the data source. For temporal data this can produce very poor results. We should probably add an optional `DataSource.extent` property that returns the overall extent of the data and then zoom/fly to that instead.
[Forum discussion](https://groups.google.com/d/msg/cesium-dev/eZ9Uu3rjMwM/iZhohzuQOeMJ)
Contributor guide
Research direction
Start with the linked forum discussion, then inspect the viewer.zoomTo and flyTo entry points and the DataSource API mentioned in the issue. Determine how an optional overall extent should be represented and used for temporal data, with completion defined by zooming and flying to that extent instead of the current entity bounding sphere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100