Stay Connected with the Boundless Blog

GeoWebCache 1.2.4 Released With Exciting New Features

Congratulations to the GeoWebCache development team on the release of GeoWebCache 1.2.4!

Although development has continued consistently, benefiting GeoServer users and those who downloaded nightly builds, it’s been almost a year since the previous release.

The new features since the last release are numerous, including a new disk quota module for automatic managing of tile storage. The disk quota prevents runaway disk usage, removes the need for manual truncation operations, and allows for multiple policies for determining how to remove tiles from the cache.

Also, GeoWebCache can now serve tiles from an ArcGIS Server tile cache, allowing a preexisting tile cache to be easily migrated to a fully standards-compliant web mapping stack without the need for re-creation. You now also have the ability to configure the service metadata for the capabilities document.

Finally, the documentation has received a much-needed update (with a nightly-updated version), the codebase has been refactored, and the source code migrated to git (hosted on GitHub).

Since GeoWebCache doesn’t get discussed very often, a little background might be in order. The tile cache server is the unsung hero of the geospatial software stack, performing its duties in a transparent way such that one doesn’t often notice it. This is a pity, since using GeoWebCache is an imperative in any production-ready web mapping system that utilizes Java. When you have hundreds of users requesting millions of tiles, GeoServer (and other robust servers running WMS) can handle that kind of load, but it makes no sense to do so. Since the data is often static, the requests are often duplicates. Since tiles are stored for later use, GeoWebCache eliminates the need for duplicate WMS processing. By placing GeoWebCache as a proxy in front of a WMS one can separate servers between public and private networks, increasing security as well as performance. In short, if you’re running GeoServer in production, you should be using a tile cache. Might we humbly recommend GeoWebCache for this purpose.

Thanks to Gabriel Roldan, Arne Kepp, Miles Jordan, and everyone else who has contributed to this new release.