GeoJSON Polygons in 3D aren't clamped to ground when requested
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15.8k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
The logic at https://github.com/CesiumGS/cesium/blob/master/Source/DataSources/GeoJsonDataSource.js#L513-L517 is quite non-obvious. I can ask for a 3D LineString in GeoJson to be clamped to ground, and it works fine, so why shouldn't this be a possibility for a 3D Polygon?
The Sandcastle example has a yellow LineString and red Polygon (actually MultiPolygon but I don't think it matters).
Browser: Chrome 84
Operating System: Windows 10
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
Start with Source/DataSources/GeoJsonDataSource.js lines 513-517 and reproduce the behavior using the linked Sandcastle example. Compare the existing 3D LineString clamping behavior with the red Polygon or MultiPolygon, and consider the issue complete when a requested 3D polygon is clamped to the ground as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100