[postgis-devel] PostGIS 3 thought experiment

Björn Harrtell bjorn.harrtell at gmail.com
Tue Jan 30 13:25:27 PST 2018

On hash key thing - not sure if I understand the need completely but I did
use (and included) uthash (1) when doing the protobuf formats encoders.
Macro magic.. but generic and fast.

Darafei mentioned GeoJSON FeatureCollection direct output which I also have
missed on several occasions. Could probably reuse some of the stuff I made
for protobuf formats to implement it, so I'd like to tackle that one some
day if no one gets to it before me.

New serialization format + compression scheme + uncompressed header sounds
cool (but hard).

1) https://troydhanson.github.io/uthash/

PS. *secret shameful wish* - in a far away galaxy I dream of geometry
predicates, operations and PostGIS itself in modular Rust. That dream
includes me learning and becoming good at Rust too...


2018-01-17 18:44 GMT+01:00 Paul Ramsey <pramsey at cleverelephant.ca>:

> What else is on everyone's wish list? Preferably things you'd do if
> you didn't think everyone would shoot you down for being too
> disruptive.
> https://trac.osgeo.org/postgis/wiki/PostGIS3
> * Break out a postgis_raster extension with a postgis dependency, so
> raster support becomes optional.
> * Require installation in a 'postgis' schema, always and for ever
> * Yet another serialization, this time changing to use external
> storage type, and adding our own compression scheme for coordinates.
>   * An uncompressed header, so header info can always be efficiently
> "sliced" and read, even for very large objects
>   * A hash key for use in fast and small equality comparisons (for use
> in cached comparison code)
>   * A compression format optimized for doubles
>   * Other compression formats with other tradeoffs (?) like TWKB for
> higher ratio with precision loss
>   * Implies indirection in coordinate access again: smaller, more
> efficient must be balanced against direct access to coordinates
> * Move up to "modern" C and use whatever cool features we like from that
> * Modern GEOS version requirement?
> * Some major GEOS surgery to allow memory management by palloc?
> * Some major GEOS surgery to build coordinateSequence directly on top
> of PostGIS pointlists?
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20180130/76f1257d/attachment.html>

More information about the postgis-devel mailing list