The GeoServer team is proud to announce the release of GeoServer 1.7.3. The team has been busy in the six weeks since the previous release, with a code sprint in New York last month and a whopping 63 bugs and new features fixed and implemented (respectively, of course).
This release brings improved support for ArcSDE rasters. Previously GeoServer only supported a limited number of SDE rasters, namely 3 and 4 band UCHAR with no color map support. GeoServer now supports all sample types up to an arbitrary number of bands, with color map support. Special thanks goes out to MassGIS who provided the funding for this work, and Gabriel for his hard work implementing this feature.
In a first step towards a “multiple configurations” feature, GeoServer now allows you to filter any capabilities request based on namespace. A client can now ask for a particular subset of layers instead of having to receive all of them, which can greatly increase client performance if serving lots of layers. (This works the same way for all services, although the above link is for WCS.)
There are quite a few new extensions for GeoServer, including:
REST – GeoServer now allows for configuration via REST (REpresentational State Transfer). This opens up a whole new world for interfacing with GeoServer, whether it’s a simple metadata update, a batch configuring of layers, or a one step shapefile upload.
JDBC Image Mosaic – This extension allows a coverage to be stored along with its pyramids in a JDBC database. Special thanks to Christian Müller, who contributed this work!
Excel – Adding to the list of WFS output formats, feature data can now be output in Microsoft Excel (.XLS) format. If you want tabular output, but don’t need the full power of Excel, you can output comma-separated values (.CSV). CSV output is available as part of the GeoServer’s core, with no extension needed.
Directory datastore – In addition to the REST interface, there is now an even easier way to add lots of shapefiles to your catalog. With the directory datastore, you can point GeoServer to a directory full of shapefiles and just hit go (well, Submit, Apply, and Save) and all of the shapefiles will be loaded in as datastores.
Also, don’t forget that GeoWebCache is now built in to GeoServer (it was previously an extension), so GeoServer can immediately cache WMS tiles, which can vastly improve the speed of rendering.