Paul Ramsey

Ensure that additional operators are not appended when the function and opfamily disagree about dimensionality. References [TRAC-5025](https://trac.osgeo.org/postgis/ticket/5025#comment:8)

Report exceptions in geosop instead of dying References #661.

GEOSGeom_setPrecision flattens multi-geometries

2

So no-op precision reductions end up having a spurious type change as well: ``` geosop -a "MULTILINESTRING((0 0,10 10))" -f wkt reducePrecision 1 LINESTRING (0 0, 10 10) ```

Generic GEOSParameter type in CAPI

7

The CAPI already has two parameter types `GEOSBufferParams` and `GEOSMakeValidParams` along with a small herd of setters and getters for those types. As more GEOS functions with fun collections of...

As noted in #623, this simplifier has not been ported yet. https://github.com/locationtech/jts/blob/0afbfb1956ec24912a8b4dc4edff0f1200442857/modules/core/src/main/java/org/locationtech/jts/simplify/VWLineSimplifier.java

Remove RETURN_UNIQUE_PTR

1

This shim to get around warnings for GCC

There's no doubt that GEOS has a lot of extra `#include` directives lying around. Some could be forward declarations. Others could just be not there at all! Finding them is...

Test for stack overflow

2

wkb_import_fuzzer: Stack-overflow in lwcurvepoly_from_wkb_state https://trac.osgeo.org/postgis/ticket/4996

More mutable SegmentStrings

3

Current segments strings have a fairly ugly API, and quite different behaviour with regard to ownership of the CoordinateArray underlying them. The NodedSegmentString takes ownership, while the BasicSegmentString takes a...

Using example from #218 add a regression test for this behaviour. Also for numeric columns.