[Geoserver-users] GeoWebCache 1.1.5

[Arne K. <ak...@op...>]

See http://geowebcache.org/trac/wiki/Version1.1.5 for nicely formatted 
release notes and download links.

The 1.1.4 release went unannounced to make the GeoServer 1.7.6 inclusion 
deadline. From the new items below, it only contains the GetCapabilities 
document. As far as I can remember, and according to the ticket system, 
there have been no real bug reports since 1.1.2 was released. That's 
unlikelt to reflect reality, please come forward if you know of any :)

*** General information: ***

* German documentation
First a todo item: Markus Weißmann, of LGN - Landesvermessung + 
Geobasisinformation Niedersachsen, has kindly started translating the 
documentation to German[1]. If you can spare some time he, and I am sure 
many others, would appreciate the contribution. On a related note, 
you're welcome to ask questions in German (or anything Scandinavian) on 
this list. I'll probably answer in English to save time, and provide a 
short translation of the question for other readers.

* Running Java on Linux
Someone forwarded me a blog post where the main criticism against GWC on 
Linux appeared to be Java. This is probably quite common, and unlikely 
to go away until (if) OpenJDK surpasses Sun's closed source JDK. I have 
therefore added a page in the wiki[2] on how I recommend that people 
install Java on Linux.

* XSD Documentation
Please refer to the XSD documentation[7] for a complete listing of all 
supported configuration elements.


*** Highlights in this release include: ***

* WMS GetCapabilities document
The WMS service can now serve a complete getCapabilities documen 
generated from the configuration. A <queryable> element has been added 
to geowebcache.xml for this purpose, getfeatureinfo request and 
getlegend requests are forwarded to the backend WMS server by default. 
Thanks to Matthias Drews for providing the patch that put it back on the 
agenda.

* Request Filters
Request filters are applied to incoming requests and can be used for 
advanced filtering. The primary use case is for layers where the 
bounding box provides a very poor approximation of the extent of the 
data, and you wish to avoid storing millions of blank or ocean tiles. 
These filters are not trivial to use at this point (it depends on your 
data) and primarily designed for large deployments where the savings can 
amount to many terabytes.

See the wiki [3] . The documentation is still under construction, so 
come back soon if it doesn't answer your question.

* Partial TMS Support
Mikael Nyberg has contributed a TMS converter. It is partial in the 
sense that only the tiles themselves are supported, the XML documents 
specified by the specification[4] are not. You can read more about it in 
the wiki [5].

* Cache truncation
The truncate requests work again after a length hiatus. If you run with 
a metastore (default) the database will be consulated to find the tiles 
thare to be deleted. If you do not have a metastore the cache directory 
will be scanned using a filter. The old documentation[6] should still apply.


1: http://geowebcache.org/trac/wiki/de/Documentation
2: http://geowebcache.org/trac/wiki/JavaOnLinux
3: http://geowebcache.org/trac/wiki/request_filters
4: http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification
5: http://geowebcache.org/trac/wiki/service_tms
6: http://geowebcache.org/trac/wiki/GWC_seeder
7: http://geowebcache.org/schema/docs/1.1.5

-- 
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers