GeoWebCache

1.2.0 (final)

1.2.0 is finally out the door! Most of the code has actually been stable for the past two months and very few issues have been reported against the beta. In addition to the usual tweaks, there were a few last minute changes related to the HTML output.

New Features:

  • New documentation written in reStructured text, compiled by Sphinx. This was very much inspired by Markus Weißmann's German contribution this summer, and will also make it easier to version the documentation. This is only the beginning, and in spite of spelling and markup errors it's still much better than what we had before. I would be very thankful if people ask questions and add the answers, spellcheck or translate. The format is quite easy to understand, and we can create a build service if you do not have the tools installed locally.
  • Completely new grid system. This lets you define grids and use them across multiple layers. See the documentation.
  • Support for arbitrary tile heights / widths. The OpenLayers demos will be able to use these too.
  • The getcapabilities configuration will pick up other SRSs defined for a layer, usually the native projection. These are also available in the OpenLayers demos.
  • The system no longer use lazy initialization. So if there is a problem with the configuration, you will know by checking the log 10 seconds after startup. A delay had to be introduced in the event that people want to fetch a getcapabilities document residing in the same servlet container as GeoWebCache.
  • OGC WMTS support (pending ratification), namely the KVP implementation. REST and SOAP will hopefully follow, pending funding.
  • Runtime Statistics. Take a client for a spin, then check out http://localhost:8080/geowebcache/home , or see here
  • Improved URL encoding and decoding, fewer layer names and filters should be problematic. Please report them!
  • The included OpenLayers client has been upgraded to 2.8
  • The XSD documentation and schema have also been updated

Upgrading:

  • Database: If Upgrading from 1.1.x, it is recommended that you make a zip file (or other archive) of the meta_jdbc_h2 directory. It is best if you stop the Java process before doing so, especially on Windows. The database will be upgraded automatically and may not work with 1.1.x thereafter.
  • geowebcache.xml: While GeoWebCache 1.2.0 has been tested with old configuration files, it is recommended that you read the documentation and write a new configuration file. This is particularly true if you use SRSs other than EPSG:4326 and EPSG:900913, since Grid Sets do a much cleaner job at capturing this information.
  • geowebcache-servlet.xml: You must use the file from this release and repeat any changes, such as entering your getcapabilities URL.

1.2.0-beta

The beta version of 1.2.0 is out, download from here: http://etch.opengeo.org/geowebcache-1.2.0-beta-WAR.zip

Lots of little bugfixes and improvements

1.2.0-alpha

The alpha version of 1.2.0 is out, download from here: http://etch.opengeo.org/geowebcache-1.2.0-ALPHA.zip

Features:

  • Completely new grid system, lets you define grids and use them across multiple layers
  • Support for arbitrary tile heights / widths
  • The system no longer uses lazy initialization. So if there is a problem, you'll know right away, not when your first client stops by
  • WMTS support (still missing some patches, I just discovered)
  • Runtime Statistics. Take a client for a spin, then check out http://localhost:8080/geowebcache/home
  • Improved URL encoding and decoding, fewer layer names and filters should be problematic. Please report them!
  • The included OpenLayers client has been upgraded to 2.8

Your old configuration files should still work, though you will need to use the new geowebcache-servlet.xml The code has been cleaned up a fair bit, specifically GridCalculator is gone and the number of functions on TileLayer have been reduced.

Things I haven't gotten too, which may still make it into the release:

  • Support for SSL backends
  • Support for HTTP Authorization against backends
  • Support for ESRI without using vendorParameters

Documentation is thin at this stage, but the included geowebcache.xml , the XSD and the schema documentation should get you started.

ALSO: If you don't like the new configuration file format, or have a better idea, now is the time to say so.