Changes between Version 27 and Version 28 of UsersWikiPostgreSQLPostGIS


Ignore:
Timestamp:
Aug 3, 2010, 7:44:39 AM (14 years ago)
Author:
robe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • UsersWikiPostgreSQLPostGIS

    v27 v28  
    2626The none means that you can get that version to work without GEOS, though its not recommended since a lot of functions will not be installed. 
    2727
    28 For the not recommended, this means that while you can get PostGIS to work with those versions, you'll be missing out on some PostGIS functions such as ST_Covers, ST_CoversBy and for PostGIS 1.5 the ST_HausdorffDistance and enhancements to ST_Buffer (both speed and functionality).  GEOS 3.1 brought cascade union.  GEOS 3.2 brought faster buffering and buffering enhancements, plus numerous enhancements with dealing with tolerance issues when unioning.
     28
     29For the not recommended, this means that while you can get PostGIS to work with those versions, you'll be missing out on some PostGIS functions such as ST_Covers, ST_CoversBy and for PostGIS 1.5 the ST_HausdorffDistance and enhancements to ST_Buffer (both speed and functionality).  GEOS 3.1 brought cascade union.  GEOS 3.2 brought faster buffering and buffering enhancements, plus numerous enhancements with dealing with tolerance issues when unioning. GEOS 3.3 brought ST_ValidReason, ST_MakeValid etc (in the PostGIS 2.0 releases), so these functions will be disabled in PostGIS 2.0 if you are not running GEOS 3.3.
    2930
    3031||'''Geos Version'''||'''PostGIS 1.3'''||'''PostGIS 1.4'''||'''PostGIS 1.5'''||'''PostGIS 2.0'''||