We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
MWE:
import GeometryOps as GO using GeometryBasics poly = Polygon(Point{2, Int}[(3, 1), (4, 4), (2, 4), (1, 2), (3, 1)]) GO.buffer(poly, 1)
Errors with this error message
ERROR: MethodError: no method matching buffer(::GeometryOps.GEOS, ::Polygon{2, Int64, Point{…}, LineString{…}, Vector{…}}, ::Int64)┌ Error: Hint-handler _buffer_error_hinter for MethodError in GeometryOps caused an error └ @ Base.Experimental experimental.jl:321 Closest candidates are: buffer(::Any, ::Any; kwargs...) @ GeometryOps ~/.julia/packages/GeometryOps/AZq8B/src/methods/buffer.jl:10 Stacktrace: [1] buffer(geometry::Polygon{2, Int64, Point{…}, LineString{…}, Vector{…}}, distance::Int64; kwargs::@Kwargs{}) @ GeometryOps ~/.julia/packages/GeometryOps/AZq8B/src/methods/buffer.jl:11 [2] buffer(geometry::Polygon{2, Int64, Point{…}, LineString{…}, Vector{…}}, distance::Int64) @ GeometryOps ~/.julia/packages/GeometryOps/AZq8B/src/methods/buffer.jl:10 [3] top-level scope @ ~/H/anopheles_africa/00_geodata.jl:90 Some type information was truncated. Use `show(err)` to see complete types. ┌ Error: Hint-handler _buffer_error_hinter for MethodError in GeometryOps caused an error └ @ Base.Experimental experimental.jl:321
Which surely isn't the hint I am intended to get here ;)
The text was updated successfully, but these errors were encountered:
Huh! Thanks for the report, will check it out.
The hinter is supposed to tell you to load LibGEOS...
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
MWE:
Errors with this error message
Which surely isn't the hint I am intended to get here ;)
The text was updated successfully, but these errors were encountered: