Improve Clipping Polygon Performance
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15.8k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
Feature
https://github.com/CesiumGS/cesium/pull/11750 added an initial implementation of clipping polygons. However, some users are seeing performance hits depending on usage.
The performance hit is not directly correlated with the number of polygon positions. The geographic extent, concavity, and number of polygons also factor in. For example, the AEC Clipping Example is a particularly concave polygon with many positions shows this performance hit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the initial clipping-polygon implementation in PR #11750, then reproduce the reported slowdown with the AEC Clipping Example. Measure behavior across geographic extent, concavity, polygon count, and position count; done means the clipping polygon implementation performs better in the reported cases without changing its expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100