Dan Baston
Dan Baston
I'm curious what people think about an API like: ``` GEOSSetProgressCallback(pFn, pUserData) GEOSCoverageSimplifyVW(geom, tol, preserve) ``` The C API would store the callback in a variable to be used during...
As an experiment, https://github.com/dbaston/libgeos/commit/0e4aae42ad0adda19dcc7ecf8a8a03b09c283a45 follows the pattern of #803 and allows for a progress callback to be registered with a context. This is a bit less magical than what I...
I think it would be fairly involved. I see that `GeometryFixer::fixRing` delegates to `BufferOp::bufferByZero` under the hood. The buffering code is fairly complex and does not work with M values.
> Is it useful for me to keep opening issues for these things? It doesn't hurt. Maintainers might add Z/M handling in cases where it's not very involved (#1317, #1319),...