Paul Ramsey

Apply spatial filter if && operator is used

3

It should be possible to notice an && operator in the deparse stage and find a spatial literal argument (???) to emplace in the OGR layer. There may be some...

By applying [OGR_L_SetIgnoredFields](http://www.gdal.org/ogr__api_8h.html#a6d43f1474201356bed2e6f92e7d37154) to the OGR Layer before reading, we can dramatically reduce the amount of data pulled over the wire in response to a particular query target list. If...

Support OGR *List types

1

OGR has StringList, IntegerList types, which have analogues in PgSQL space as text[] and integer[] types, so it's possible to cleanly support them. They are relatively uncommon in OGR data...

Deparsing "IN" statements will be a bit fiddly, since it will involve delving into all the branches of the T_ScalarArrayOpExpr tree. Probably have to have array handling as well.

The GUC system doesn't require the variable names to be preconfigured if they are under a prefix, so the following works: ``` http=# set http.foobar = 'this'; SET http=# show...

Intersection of Line/Polyon is EMPTY when line is zero-length

3

From https://trac.osgeo.org/postgis/ticket/5376: ``` select st_astext(st_intersection( 'LINESTRING(3 1, 3 1)', 'POLYGON((2 0, 2 2, 4 2, 4 0, 2 0))')); LINESTRING EMPTY ``` On the one hand, we maybe want our...

I was just updating the STRTree examples and documentation, and noticed that while we have a "nearest" we don't have a "K nearest" which seems like a pretty common use...

The old site: trac.osgeo.org/geos is deprecated. If you would update links to https://libgeos.org that would be great!

Don't attempt to write on invalid input

3

Not sure what exact input causes this, but it's necessary to regress PostGIS on all platforms

Don't call all records deleted if record count is not set

6

Some DBF files are written without a record count (because, say the SHP file or SHX file already give a record count. In that case, checking the shape index being...