Changes between Version 20 and Version 21 of PostGIS3

Timestamp:

05/10/19 14:26:53 (6 years ago)

Author:

robe

Comment:

—

PostGIS3

@@ -2 +2 @@
 
 This page is not a list of things that **will happen** it is a place to gather disruptive changes that might make sense for a PostGIS 3 release.
-
-== Tasks ==
-
-* strk and robe to help set up OSGeo7 via Jitsi
 
 == Done
@@ -15 +11 @@
 * Modern GEOS version requirement
 * 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;
+* Support for Proj 6.0, GDAL 3.0
 
-== Ideas
-
-* Require installation in a 'postgis' schema, always and for ever **HOLD OFF not as important as it used to be now that its not movable**
-* Yet another serialization, this time changing to use `external` storage type, and adding our own compression scheme for coordinates.
+== In Progress (most likely will be released in 3.0)
+ * * 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)
@@ -25 +20 @@
   * 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
+
+
+== Ideas
+
+* Require installation in a 'postgis' schema, always and for ever **HOLD OFF not as important as it used to be now that its not movable**
+
 
 * Some major GEOS surgery to allow memory management by palloc?