Changes between Version 20 and Version 21 of PostGIS3


Ignore:
Timestamp:
May 10, 2019, 2:26:53 PM (3 years ago)
Author:
robe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • PostGIS3

    v20 v21  
    22
    33This 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.
    4 
    5 == Tasks ==
    6 
    7 * strk and robe to help set up OSGeo7 via Jitsi
    84
    95== Done
     
    1511* Modern GEOS version requirement
    1612* 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;
     13* Support for Proj 6.0, GDAL 3.0
    1714
    18 == Ideas
    19 
    20 * 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**
    21 * Yet another serialization, this time changing to use `external` storage type, and adding our own compression scheme for coordinates.
     15== In Progress (most likely will be released in 3.0)
     16 * * Yet another serialization, this time changing to use `external` storage type, and adding our own compression scheme for coordinates.
    2217  * An uncompressed header, so header info can always be efficiently "sliced" and read, even for very large objects
    2318  * A hash key for use in fast and small equality comparisons (for use in cached comparison code)
     
    2520  * Other compression formats with other tradeoffs (?) like TWKB for higher ratio with precision loss
    2621  * Implies indirection in coordinate access again: smaller, more efficient must be balanced against direct access to coordinates
     22
     23
     24== Ideas
     25
     26* 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**
     27
    2728
    2829* Some major GEOS surgery to allow memory management by palloc?