The GeoServer community is happy to announce that the second release candidate of GeoServer 2.1 is now available for download. There is not much in the way of new features for this release, but the team has been busy fixing bugs. Checkout the change log for the list of fixes.

Download and try 2.1-RC2 now. You can help us reach the final 2.1 release by reporting any bugs in the issue tracker and sending feedback to the mailing list. Thanks for supporting GeoServer.

The GeoServer community is happy to announce that the first release candidate of GeoServer 2.1 is now available for download. The team has been busy working on some great new improvements and features since 2.1-beta3.

First up is GeoWebCache integration, allowing clients to enjoy the benefits of tile caching through the regular GeoServer WMS endpoint. This enables GeoWebCache to transparently proxy for the GeoServer WMS without the need for a separate service endpoint. Taking advantage of the recently added disk-quota functionality, GeoWebCache now provides the ability to set limits on the amount of disk space used for storing tiles, allowing users to control and limit the size of the tile cache on disk. Big thanks to Gabriel Roldán for the great GeoWebCache improvements.

This release also brings some improvements to RESTConfig, which is now shipped with GeoServer by default so users need no longer install it as a separate plugin. Improvements to the API include the file upload operation that now allows for uploading files into an existing data store. This addition allows users to upload a shapefile and have it converted automatically into a PostGIS database, publishing it as a PostGIS layer rather than as a Shapefile layer. Finally, the API also supports recursive DELETE operations, making it more convenient to remove resources that contain other resources like stores or workspaces. Thanks to David Winslow and Justin Deoliveira of OpenGeo for these improvements.

Thanks to some great work from the folks at GeoSolutions, raster reprojection performance has improved significantly by using linear appoximations of transformation functions. This improvement was initially added in 2.1-beta3 but has continued to be improved for 2.1-RC1. Those interested should checkout this article that links to a white paper with the full technical details.

Last but certainly not least, thanks to Andrea Aime for the addition of a Web Coverage Service request builder, a handy tool for graphically building WCS requests to test a coverage service. As clients for WCS have always been sparse, this tool goes a long way for making the service more usable.

We are happy to report the contribution of yet another translation of the web admin interface—special thanks to Oscar Fonts for submitting a Catalan translation and to Geodata Sistemas for funding the work.

Also worthy of thanks this round is Ivan Grcic who has submitted some excellent patches, including bug fixes for WMS layer functionality. Thanks Ivan!

As always, a number of other bug fixes and improvements have made it into this release. Check out the change log for all new and noteworthy changes.

Download and try 2.1-RC1 now. You can help us reach the final 2.1 release by reporting any bugs in the issue tracker and sending feedback to the mailing list.

Thanks for supporting GeoServer!

The GeoServer community is proud to announce the release of 2.1-beta3, which is now available for download.

The big feature for this release is support for WMS 1.3. Special thanks goes out to Ordnance Survey, Great Britain’s national mapping agency, for providing OpenGeo with funding to complete the task. With WMS 1.3 mandated by the INSPIRE Initiative, the Ordnance Survey needed to meet the INSPIRE requirements.  Rather than implement a solution on their own, they opted to fund the GeoServer project so that other organizations in the UK and the rest of Europe and the world could all benefit.

This is the value and the beauty of open source. Government agencies across Europe can now upgrade their servers to the latest GeoServer at no additional cost.  In time, other mapping agencies can and will further benefit one another by funding additional GeoServer improvements, like WFS 2.0 and Application Schema configurations for INSPIRE, but the Ordnance Survey deserves special recognition from all GeoServer users for taking the lead.

In addition to WMS 1.3, this release includes some SLD 1.1 / SE 1.1 enhancements.  It will be possible to use most SE 1.1 documents, though not every new option is fully supported yet.  User feedback on which new options we should support first is greatly appreciated.  Also funded by Ordnance Survey is a community module to implement the WMS extensions for INSPIRE View Service compliance—namely the language parameter and several extended capabilities fields.

The release also includes a few nice fixes and improvements from beta2, such as upgrading CQL to ECQL, and a fix by Eli Miller, a newcomer to the GeoServer community, to allow the REST Config API to properly handle SQL Views.

We encourage you to download GeoServer 2.1-beta3, try it out, and let us know if there are any bugs. This software is still a beta, so we recommend testing extensively before running it in a production environment. That said, we’re hoping to move to 2.1.0 release candidates soon, so any and all testing will this process move along faster.

Download GeoServer 2.1-beta3

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.

Font Improvements

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.

WCS limits

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.

And more

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.

Download GeoServer 2.1-beta2

Just in time for FOSS4G the GeoServer community is pleased to announce the release of 2.1 beta1. The first beta release of the long awaited 2.1 branch is now available for download. Anticipation for this release has been growing over the last few months due to the number of notable new features it brings. Let’s go down the list.

WMS Cascading

Something users have asked for since the addition of WMS support itself is cascading, the ability of GeoServer to proxy for another remote WMS server like MapServer or another GeoServer. This feature has many uses such as pulling in a remote base layer and overlaying local vector data onto it or securing a locally unsecured map server. Special thanks to the University of Perugia for sponsoring this feature.

Read more about WMS cascading.

Virtual Services

Anyone who has published a large number of layers or feature types with GeoServer has probably at some point been annoyed by the fact that every single layer is published by a single global service. WMS has the ability to group and nest layers but WFS and WCS have no such equivalent. Well now with virtual services one can create multiple service endpoints within a single physical geoserver instance.

Special thanks to Landgate for funding this work.

Read more about virtual services.

Layers from SQL

GeoServer has always been good at publishing a flat database table. But users often need to do more such as pre filter the data in a table, or join two tables together, or generate column values on the fly with a function. Before this feature the recommendation was to create a view. However views can be a maintenance burden and are at times problematic.

Now one can create a layer directly from an SQL query. And on top of that query definitions can be parameterized which allows one to create dynamic queries on the fly. These parameters can be restricted with regular expressions in order to prevent an SQL injection security hole.

Special thanks to Andrea for spending much of his personal time on this one. And also to OBIS who provided the funding for the parametric component of the work.

Read more about SQL layers.

WPS

With 2.1 and the arrival of WPS we welcome a new OGC service to the family. The Web Processing Service is an OGC service for performing geospatial analysis functions over the web. The specification is extensible in nature and allows for simple processes like buffering a geometry to more complex processes such as image processing.

Historically GeoServer has been focused primarily on data delivery without any tools for performing analysis of spatial data. WPS fills that gap making GeoServer a more compete solution for geospatial web services.

Thanks to Refractions Research for the initial contribution of the WPS module and to Andrea once again for taking personal time to bring WPS support to its current state.

Read more about WPS. Download the WPS extension now to try it out.

Unit of Measure

Support for units in SLD allows one to specify values in measurements other than pixels such as feet or meters. This adds a very powerful capability to SLD that in many cases alleviates the need for multiple scale dependent rendering rules. This has the upside of greatly simplifying complex SLD documents.

Special thanks to Milton Jonathan who did the initial GeoTools work to make unit of measure support possible and to Andrea for working with Milton to improve the initial patch. Note that this feature has also been backported to the stable 2.0.x branch. Thanks to SWECO and Malmö City of Sweden for sponsoring the backport.

Read more about UOM support.

DPI Scaling

By default GeoServer renders images at a resolution of 90 DPI. While this is acceptable for the standard screen it is not acceptable for print which requires a higher resolution. Now it is possible to supply a format option to a WMS request on the fly that controls the DPI setting.

Special thanks again to SWECO and to Malmö City of Sweden for sponsoring this work. Note also that this feature has also been backported to the stable 2.0.x branch.

Read more about DPI scaling.

And More

And as usual this release comes with a number of bug fixes and minor improvements. Check out the entire changelog. Help us get to 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.

Thanks for using GeoServer!