-
Notifications
You must be signed in to change notification settings - Fork 23
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
GEOSConcaveHullByLength Error #182
Comments
Like in #181 (comment), this hasn't been wrapped, so it's a bit harder to use, but here is an example. The main things are that the first argument needs to be a context handle, and a julia> using LibGEOS
julia> g = MultiPoint([[1.1,2.2],[3.3,4.4],[2.2,3.3]])
MULTIPOINT ((1.1 2.2), (3.3 4.4), (2.2 3.3))
julia> ctx = LibGEOS.get_context(g)
LibGEOS.GEOSContext(Ptr{Nothing} @0x0000024a80733c20)
julia> ptr = LibGEOS.GEOSConcaveHullByLength_r(ctx, g, 1.5, 1)
Ptr{Nothing} @0x0000024b131a8b50
julia> conc = LibGEOS.geomFromGEOS(ptr)
POLYGON ((1.1 2.2, 3.3 4.4, 2.2 3.3, 1.1 2.2)) |
It looks like it, yes. Is this using LibGEOS v0.8.5 with GEOS_jll v3.12.0? Could you share the output of |
[a90b1aa1] LibGEOS v0.8.5 |
(The output was huge so I took only those two) |
I also use GDAL for this project and it seems to block my version of GEOS_jll |
Right indeed that explains it. I should've added compat bounds such that you cannot get the newly wrapped functions with an old binary that doesn't have them, I forgot. So for now you cannot use both at the same time, until a new GDAL_jll is released that is compatible with GEOS 3.12. I saw some work was underway in JuliaPackaging/Yggdrasil#7050 but it looks a bit stalled. |
Ok. No problem, thank you for the help :) |
GDAL.jl 1.6.1 should no longer hold back the GEOS version. |
Yes I just tried it and it worked perfectly. Thanks :) |
I tried to use your GEOSConcaveHullByLength function and it seems that it crashes when calling the C code.
I am looking into it but if you find a solution before I do, it could be nice to correct it XD.
The text was updated successfully, but these errors were encountered: