-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polygons that contains a Pole are not filled (so not clickable) #10857
Comments
Hi @spiderdab, changing the arc type to geodesic allows the polygon to fill. Otherwise, I believe the polygon appears to not be filled due to intersecting with the earth's ellipsoid. This comment has a workaround that may help. |
Hi and thank for helping. but if I put a more complicated polygon (taken from a satellite geojson) it gives me an error.. I also tried to reverse the points order (maybe a problem with anticlockwise..) but the result is the same.. |
@spiderdab I suspect that the original representation in 3D did cover the pole, but the 2D data in the GeoJSON does not. Below is an image from QGIS showing the poles and the points creating the polygon. Obviously still a problem, but not due to covering the pole. @ggetz Is there any "Inspector" for polygon triangulation to help see what's going on or a description of how filling works? |
Indeed I think that this satellite returns a footprint with a hole around the pole, so I was wrong with the issue argumentation.. EDIT: |
No, but that's a good suggestion @GatorScott! I'll add that suggestion to #4871. @spiderdab I do think the root issue here is a duplicate of #8042 as part of fixing that will need to include special consideration around the north and south poles. The overlapping in the second example (as @GatorScott alludes to) is likely a separate issue with triangulations for large polygons. As a workaround, users have had some luck by breaking up larger polygons into smaller ones. If you agree, we can close this and move this discussion to those issues. |
Thanks for your answer and suggestions. |
Sandcastle example:
https://sandcastle.cesium.com/#c=dZJPSwMxEMW/ypBTC9ts66GI3RahoiCCQsGL6SHdHWswmylJtmUVv7tJ1/5fDyHz3rzfHDLJyTgPa4UbtDAGgxuYolNVyV+3XkewfKunZLxUBq1g3ZEwwjQML6SXM6psSHFZFB1hYDfhAenRkbnbJ7gm2SQAvpsLQDBfr1Cwm1Ddo/SVDSI5dJdIJXpbx8QeOsVeSNdLMkdY7OdEtlBGenQx9nbowakIsp8M+/PkzBy2uoOrdvu61e79E++1D7805wexL3+aYnt1hWn2wRIm2ChauwOQOV9rnOy4W1WuyHqorO5wnnosVzo+T7qo8k/0PHeuO/oj02M0K9QaVDFu+QyQa+lc6LxXWs/UV1jJJEtD/gKNy1dm+bxGq2UdYx+DyVNjcs6zNMh20hPphbRnk38B
Browser:
Firefox v.105.0.1
Operating System:
Pop!OS 22.04 (ubuntu)
I saw this issue developing in Angular. Sandcastle behave the same.
The text was updated successfully, but these errors were encountered: