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.
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.
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.
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.
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.
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.
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.
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.
Read more about DPI scaling.
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!
Community member Michelle Ballinger has put together a short tutorial on creating an open source web map using GeoServer.
This tutorial is designed for a beginner and is easy to follow. The steps she uses are:
Creating and editing data with QGIS
Designing SLDs with uDig
Serving maps with GeoServer
Creating a custom OpenLayers application
Posting to the web
The introduction mentions the benefits of using open source and also, interestingly, discusses the pros and cons of making a “mash-up” versus serving one’s own data.
Once again, we see Penn State as a proponent of open source GIS. Have you looked at their Master of Geographic Information Systems program lately?
To meet the growing demand for a geospatial server that meets the open standards set by the Open Geospatial Consortium, the GeoServer community has worked hard to release the new GeoServer 2.0.2. This release includes almost 100 bugfixes and new features.
Have you ever wondered what geographical area an EPSG code covers? A new feature has been added to showcase the different projections visually, by showing a map of the projection’s area of validity in the same CRS. Here are three examples of this: EPSG:2964, EPSG:3032, EPSG:22184.
To add to this, we have also added a default style preview in the layer publishing configuration.
The rendering subsystem has been improved to include parameter substitution, meaning you can pass parameters down from a GetMap request into your SLD for dynamic styling purposes.
The ability to do geometry transformations, included in GeoServer 2.0.1 without much fanfare, now has been completely documented.
Building image pyramids just got easier: gone are the times where you had to manually build each level mosaic and configure the main property file by hand. The current pyramid extension can do this for you provided it is given a suitably configured directory set. See the pyramid tutorial for more details.
Finally, this release of GeoServer implements the GetStyles optional WMS method allowing a user to retrieve the definition of all styles attached to a specific WMS layer, see the following link for an example: http://demo.opengeo.org/geoserver/wms?request=GetStyles&layers=topp:states&service=wms&version=1.1.0
Thanks to everyone who have worked hard over the past few months adding features and fixing bugs, in order to make this release happen. As usual, we encourage you to download, try it out, and provide feedback on the users mailing list.