Important Change in GeoGig 1.2.0¶

One of the big changes in GeoServer 2.12 was to replace Restlet with Spring MVC. This necessitated GeoGig to also replace Restlet with Spring MVC. We made the new web API exactly equivalent to the old web API, so all the requests and responses are exactly the same - web client applications should not need any changes. We also made some improvements to the API documentation.

This, however, means that GeoGig 1.2.0 is only compatible with GeoServer 2.12 - it is not compatible with GeoServer 2.11 (or earlier). If you are using GeoServer 2.11 or earlier, you must use GeoGig 1.1.1. If you are using GeoServer 2.12 or later, you must use GeoGig 1.2.0.

Upgrading to GeoGig 1.2.0¶

GeoGig 1.2.0 doesn’t change any underlying database formats - you should be able to do an in-place upgrade of GeoGig. However, we strongly recommend first validating a test system before attempting to upgrade a production server. Here is a simple process to do this;

1. Backup your existing databases (use existing PostgreSQL tools)

2. Create a new PostgreSQL database

3. Use GeoGig 1.2.0 to clone the existing repository into the new database

   geogig clone "postgresql://OLDdatabase/<repo>" "postgresql://NEWdatabase/<repo>"
   

4. Create QuadTree indexes in the new repository for the branches/layer required (if necessary)

5. Upgrade your test server to GeoGig 1.2.0, pointing to the new database

6. Test until you are satisfied that GeoGig is working in your environment and the datasets are working as expected

7. Repeat steps 2-4 to set up a new production database

8. Upgrade your production server to GeoGig 1.2.0, pointing to the new production database

Other Changes¶

Please see the release notes.