We are pleased to announce the second beta release of GeoServer 2.1. Big thanks goes out to GeoSolutions for stepping up to the unglamorous and thankless process of creating a release, not to mention adding lots of great new features.
GeoServer 2.1.0 is shaping up to be quite an incredible step forward. In addition to all the great features of the first 2.1 beta, this release brings a few more.
Graphical File/Directory Chooser
Ever found it difficult to remember the full path when loading a shapefile or GeoTIFF? A new improvement brings an easy graphical file and directory selection tool to browse the file system that GeoServer is on. This is definitely a great enhancement to make GeoServer even easier to configure.
Read more about the new file chooser.
Core improvements to support database-backed catalog
GeoServer’s core catalog interfaces received some tweaks to be able to more easily support different backend storage formats. The current in-memory implementation has a number of drawbacks, the most notable being that it is memory bound which means it can not scale up to large amounts of layers. The support for specific new storage formats is still only available a community module, but these core improvements make it possible to more easily swap in and out different backends.
Read more about the improvements for database-backed catalog.
Adding new fonts for your maps should now be much easier, as you can just drop font files directly in to your GeoServer data directory and they will be picked up by GeoServer. The admin interface also will list the fonts currently available, including the ones picked up directly from the Java Virtual Machine.
Upgrade to Spring Security 2.0.6
GeoServer has always had Acegi Security as its core, but that library got absorbed by the Spring community, and improved and upgraded to become Spring Security, the official security module of the Spring portfolio. This brings a number of new security protocols to GeoServer, including OpenID and Windows NTLM. It also should be easier to customize security setup, with even more powerful options.
Read more about the upgrade to Spring Security.
WFS and WMS both have had the ability to limit what a user can request. Now, similar controls are in place for WCS calls as well. Thanks to MassGIS for funding this improvement.
Web Processing Service (WPS) in extensions
The one thing to note from last beta release is that the WPS is maturing, It has been split up in to three modules, “core”, “web”, and “sextante”. The latter has all the algorithms of the Sextante project, but is not yet mature, so it lives in a community module. Web and core live in a new WPS extension, meaning that the core of WPS is now officially supported by GeoServer. You can find the WPS extension on the download page, and add it to GeoServer just like any other extension.
Read more about WPS in extensions.
This release also included a number of other bug fixes and improvements. Check out the entire changelog. Help us get to a stable 2.1.0 by downloading the beta and trying it out. Be sure to report any issues on the mailing list or in the bug tracker. We appreciate any and all feedback. We’re hoping to move soon to Release Candidates, after getting one last major improvement in — WMS 1.3.