You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The interesting thing is that this is not a problem for LinearRings, but I get the same issues with MultiPolygons.
I am getting around the issue for Polygons for now by using
I've made some PRs that should improve the type stability, mostly getting @code_warntype green for these kind of calls. However, some things reported by JET can't be fixed. Most things will be runtime dispatch, as we don't store geometry information in the type, and it warns it
I have been checking over my code with JET.jl and I am finding some type instability with LibGEOS/GeoInterface.
For example,
returns a huge amount of warnings (see below).
The interesting thing is that this is not a problem for LinearRings, but I get the same issues with MultiPolygons.
I am getting around the issue for Polygons for now by using
which does not cause warnings, and since I don't need to keep holes, isn't terrible for now.
However, this strategy fails on me with MultiPolygons since the following code also creates a lot of warnings:
So I can't apply my polygon strategy on each of the polygons in the multipolygon.
Warnings from LG.GeoInterface.coordinates:
Warnings from LibGEOS.getGeometries
The text was updated successfully, but these errors were encountered: