-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Geometry path issues in geostationary projection with geometry.geoms #724
Comments
Many thanks @ahuang11 for the idea. In my admittedly complex use case wrapping geoms into gv.project somehow results in the geometry not showing. Can't really pinpoint a cause right now though. |
Does anyone know where this issue might come from? I'd like to fix this as otherwise the resampled geometry cannot be used. |
To pin it down, I'd look at what gv.project does vs the crs/projection kwargs. I'd also check if you can reproduce in vanilla matplotlib + cartotpy. |
geoviews 1.12.0
holoviews 1.18.3
bokeh 3.4.1
cartopy 0.23.0
geos 3.12.1
shapely 2.0.4
With
coastline.geoms
objects in geostationary projection, paths display weird segments extending apparently infinitely towards the top-left corner.Not sure this is due to geoviews per se though. I've tried various environments including with older versions of all these libraries and they now all seem to exhibit this behaviour while it used to be fine. I've made sure to delete local natural earth geometries cached by cartopy to fetch the latest (could it come from there?)
Note that it does not happen with a bare
gv.feature.coastline
, but only with its.geoms
(which I use withresample_geometry
).No error is thrown in python or javascript.
The text was updated successfully, but these errors were encountered: