Bug Fixes
* #410, update embedded bbox when applying ST_SetPoint,
ST_AddPoint ST_RemovePoint to a linestring
(Paul Ramsey)
* #411, allow dumping tables with invalid geometries
(Sandro Santilli, for Regione Toscana-SIGTA)
* #414, include geography_columns view when running upgrade scripts
(Paul Ramsey)
* #419, allow support for multilinestring in ST_Line_Substring
(Paul Ramsey, for Lidwala Consulting Engineers)
* #421, fix computed string length in ST_AsGML()
(Olivier Courtin)
* #441, fix GML generation with heterogeneous collections
(Olivier Courtin)
* #443, incorrect coordinate reversal in GML 3 generation
(Olivier Courtin)
* #450, wrong area calculation for geography features that cross
the date line
(Paul Ramsey)
* Ensure support for upcoming 9.0 PgSQL release
(Paul Ramsey)
pgsql's Makefile.shlib are patched around. ('make test' passes on
netbsd-5/i386 with postgresql84.)
This is a major release adding a significant number of new features including:
* New "geography" type for managing geodetic (lat/lon) data
* Performance-enhanced distance calculations
* GML and KML format readers
* Improved shape loading GUI
* And more!
Release Notes
Important Changes
* =~ operator now indicates bounding box equality, not feature equality
* GEOS 3.1 is now the minimum accepted version of GEOS
* GEOS 3.2 is needed if you want to use enhanced buffering features and ST_HausdorffDistance
* GEOS, LibXML2, and Proj4 are now mandatory dependencies
New Features
* Added Hausdorff distance calculations (#209) (Vincent Picavet)
* Added parameters argument to ST_Buffer operation to support one-sided buffering and other buffering styles (Sandro Santilli)
* Performance improvements to ST_Distance (Nicklas Avén)
* Addition of other Distance related visualization and analysis functions (Nicklas Avén)
* ST_ClosestPoint
* ST_DFullyWithin
* ST_LongestLine
* ST_MaxDistance
* ST_ShortestLine
* KML, GML input via ST_GeomFromGML and ST_GeomFromKML (Olivier Courtin)
* Extract homogeneous collection with ST_CollectionExtract (Paul Ramsey)
* Add measure values to existing linestring with ST_AddMeasure (Paul Ramsey)
* History table implementation in utils (George Silva)
* Win32 support and improvement of core shp2pgsql-gui (Mark Cave-Ayland)
* In place 'make check' support (Paul Ramsey)
* Geography type and supporting functions
o Spherical algorithms from Dave Skea
o Object/index implementation from Paul Ramsey
o Selectivitiy implementation from Mark Cave-Ayland
o Serializations (KML, GML, JSON) from Olivier Courtin
o ST_Area, ST_Distance, ST_DWithin, ST_GeogFromText, ST_GeogFromWKB, ST_Intersects, ST_Covers, ST_Buffer
* Documentation updates and improvements (Regina Obe, Kevin Neufeld)
* Testing and quality control (Regina Obe)
* PostGIS 1.5 support PostgreSQL 8.5 trunk (Guillaume Lelarge)
* Many, many other changes
database. In effect, PostGIS "spatially enables" the PostgreSQL server,
allowing it to be used as a backend spatial database for geographic information
systems (GIS), much like ESRI's SDE or Oracle's Spatial extension. PostGIS
follows the OpenGIS "Simple Features Specification for SQL" and has been
certified as compliant with the "Types and Functions" profile.
PostGIS/PostgreSQL includes the following functionality:
* Simple Features as defined by the OpenGIS Consortium (OGC)
* Support for Well-Known Text and Well-Known Binary representations of GIS
objects
* Fast spatial indexing using GiST
* Geospatial analysis functions
* PostgreSQL JDBC extension objects corresponding to the geometries
* Support for OGC access functions as defined by the Simple Features
Specification
