Changes between Version 12 and Version 13 of PostGIS3


Ignore:
Timestamp:
08/28/18 01:32:01 (6 years ago)
Author:
komzpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PostGIS3

    v12 v13  
    2020
    2121* Have some strategy for storing and tracking coordinate precision
    22 * Allow storage of non-double coordinates (integers, single-precision, exact)
     22* Allow storage of non-double coordinates (integers, single-precision, exact, timestamp)
    2323* Make "PostGIS" source tree an even thin(ner?) wrapper that exposes other code to Postgres. Leave almost no processing logic here.
    2424* Consider using C++ for some of what is currently in the "lwgeom" source tree. (This could mean=moving logic of things like  {{{ ST_BuildArea }}} and {{{ ST_MakeValid }}} to GEOS, which would avoid verbose, complex code from dealing w/CAPI)
    … …  
    4040* Can we make stronger guarantees about correctness in predicate / overlay functions? E.g., guarantee correct results by checking validity of inputs before proceeding (using validity flag for performance)
    4141* Performance framework for regression / PR testing and empirical based cost setting
     42* Add box on Geometrycollection, so there is a chance to build a nested geometrycollection that will be a subdivided tree
    4243
    4344If some tweaks in postgres allowed in our experiment: