Changes between Version 8 and Version 9 of PostGIS3

Timestamp:

Mar 13, 2018, 10:21:17 AM (6 years ago)

Author:

komzpa

Comment:

—

PostGIS3

@@ -22 +22 @@
 * Allow storage of non-double coordinates (integers, single-precision, exact)
 * Make "PostGIS" source tree an even thin(ner?) wrapper that exposes other code to Postgres. Leave almost no processing logic here.
-* 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)
+* 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)
 * Build adapters to LWGEOM to boost::geometry and CGAL types so we can use those libraries directly
 
@@ -34 +34 @@
 * ST_AsGeoJSON/GeomFromGeoJSON that are aware of json/jsonb types. So, geometry::json is ST_AsGeoJSON(geometry). A documented function to turn a table into GeoJSON FeatureCollection, automagically finding the geometry field;
 * Spatial clustering: GeometricMedioid, KMedioids, XMeans, and then combine them into non-existing XMedioids with flexible exit conditions ("max cluster radius is", "max cluster diameter is", "max number of clusters is");
+* Make ST_ClusterWithin and ST_ClusterIntersecting window just like ST_ClusterDBSCAN
 * A way to store SRID and type in typmod only, so that 2D point columns take just 2*sizeof(double).