Polygon errors when using perPositionHeight
See original GitHub issueMy goal is the visualization of an elevated extruded polygon with data provided to a GeoJsonDataSource.
- The polygon is given by a GeoJson dataset, consisting of points where each is given by longitude, latitude and elevation (e.g. [ 30.0, 70.0, 152452.62 ])
- The polygon should be extruded by 30502.
A schematic profile view of such a volume could look like this:
- Green: Bottom of the polygon (given by the dataset) -> should follow the ellipsoid in 3D
- Red: Extrusion
- Orange: Top of the polygon (given by dataset & extrusion) -> should follow the ellipsoid in 3D

Now to the pratical part: I am using the following GeoJson data: polygon.zip
When using the data provided above, the visualization with GeoJsonDataSource shows some strange rendering effects. It looks like the geometry folds and cuts the globe (bottom and top of the polygon not properly following the ellipsoid):

I have also tried to visualize the polygon by using PolygonGeometry but unfortunately there are also some rendering issues:
- There is an edge in the visualization (the geometry seems to fold or cut the earth)

- When having certain view-angles the folding/cut is even more visible

So basically the issue is, that the top and bottom surface of the volume do not follow the ellipsoid properly.
- Is there any way to avoid those rendering artifacts?
- Is this issue known? Especially when using very large polygons? Actually I’m not quite sure if this is a bug, I’m missing some configurations or I´m using a wrong approach. I also could not find any sample yet which is dealing with such kind of visualizations.
I would really appreciate any help. 😃
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Polygons with heightReference, perPositionHeight, no extrusion
When a polygon has perPositionHeight and is not extruded, attempting to set a ... or CLAMP_TO_GROUND) gives the following error:.
Read more >Does CallbackProperty work with PolygonHierarchy?
I'd like to add, if I have a terrain and my positions have their own heights, I can set the perPositionHeight property to...
Read more >Geodatabase topology rules and fixes for polygon features
Polygon errors are created where polygons from the two feature classes or subtypes overlap. Must Not Overlap With errors. Predefined fixes. Remove Overlap ......
Read more >Drawing polygon using mouse click in Cesium?
entities.add({ polygon : { hierarchy : getSelectorLocation, outline : true, outlineColor : Cesium.Color.RED, outlineWidth : 9, perPositionHeight ...
Read more >How to reference positions of other entities in polygon ...
For references I also tried : just using entity and positions like: entity.position; Using entity$position . None of them worked!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

The above looks like a data problem. I think his position heights are lower than the extrudedHeight. I’ll add a comment to #2924
Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/forum/#!searchin/cesium-dev/paula|sort
If this issue affects any of these threads, please post a comment like the following:
I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
🌍 🌎 🌏