The 2.1.0beta3 release of PostGIS is now available.
The PostGIS development team is proud to release a feature complete beta version of upcoming PostGIS 2.1.0. As befits a minor release, the focus is on speed improvements, more features, and bug fixes. While this beta release is feature complete, we expect some bugs and we’d appreciate it if you test it before final release and report back with any issues you run into so we can have a smooth release.
If you are currently using PostGIS 2.0+, you can go the soft upgrade path: ALTER EXTENSION postgis UPDATE TO “2.1.0beta3”;
Users of 1.5 and below will need to go the hard-upgrade path.
Best served with a bottle of GEOS 3.4.0dev and PostgreSQL 9.3beta2. (which will also be released soon)
This release contains bug fixes completed since 2.1.0beta2 release:
View all closed tickets.
The 2.1.6 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.6 release. As befits a patch release, the focus is on bugs, breakages, and performance issues. Users with large tables of points will want to priorize this patch, for substantial (~50%) disk space savings.
The last couple weeks have seen two interesting updates in the world of PostgreSQL “foreign data wrappers” (FDW). Foreign data wrappers allow you to access remote data inside your database, exactly like other tables. PostgreSQL ships with two example implementations, one for accessing text files, and the other for accessing remote PostgreSQL servers.
The two updates of interest to PostGIS users are:
Now you can access your PostGIS data without even going to the trouble of importing it first!
The 2.1.5 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.5 release. As befits a patch release, the focus is on bugs, breakages, and performance issues