CesiumGS / CesiumGS/cesium-native
Add ability to create Cesium clips in our runtimes
- Dominant language
- C++
- Stars
- 623
- Forks
- 277
- PR merge metrics
- No merged PRs in 30d
Description
Users may want to clip data from Cesium ion (e.g., key areas of terrain) as glTF, then reintegrate it with terrain or data that is streamed through SaaS. This is possible by importing the model, re-aligning it with the original data, and using CesiumCartographicPolygon to prevent visual overlap.
However, re-positioning the glTF is currently a quite manual process. It would be more intuitive if users could clip from within the editors of our runtimes, as requested on the forum [here](https://community.cesium.com/t/clipping-tiles-inside-unity-and-making-them-into-regular-terrains/32060).
This is just brainstorming, but perhaps this could look like:
- opening a Clips window in the runtime editor
- creating a new Clip, specifying an area with a similar UI to Cesium ion's editor / Cesium Cartographic Polygon
- sending this area as a job to Cesium ion
- importing the glTF from Cesium ion directly, and ideally in the exact same location that it was clipped from
This also might suggest that Clips should store the globe-relative location of the glTF, though I'm not sure how that would work. Perhaps it could be in the glTF `extras`?
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by reviewing the runtime editor, Cesium ion clipping workflow, and glTF import path described in the issue; define the scope for specifying a clip, submitting the job, importing the result, and preserving its globe-relative location before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100