HI all,

The 2.1 beta1 release is almost complete. I am just working on the blog post
now. Here is the first cut:

http://blog.geoserver.org/?p=736&preview=true

The idea was not to go into depth about each of the new features in detail.
I think they all deserve a dedicated post over the next few weeks/month as
we build to 2.1.0.

Please look it over, feedback welcome. Also I am sure i missed notable
features that deserve mention. Please speak up if I did.

-Justin

ps. I also attached a copy of the post to this email for those who don't
have a blog account.

-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
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 <a 
href="http://geoserver.org/display/GEOS/GeoServer+2.1-beta1";>download</a>. 
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.

<h3>WMS Cascading</h3>

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

<a href="http://geoserver.org/display/GEOS/GSIP+47+-+WMS+cascading";>Read 
more</a> about WMS cascading.

<h3>Virtual Services</h3>

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 layer 
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 <a href="http://www.landgate.wa.gov.au";>Landgate</a> for 
funding this work.

<a 
href="http://docs.geoserver.org/latest/en/user/services/virtual-services.html";>Read
 more</a> about virtual services.

<h3>Layers from SQL</h3>

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 <a href="http://www.iobis.org/";>OBIS</a> who provided the funding 
for the parametric component of the work.

<a 
href="http://gridlock.openplans.org/geoserver/trunk/doc/en/user/data/sqlview.html";>Read
 more</a> about SQL layers.

<h3>WPS</h3>

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 <a href="http://www.refractions.net/";>Refractions Research</a> for 
there initial contribution of the WPS module and to Andrea once again for 
taking personal time to bring WPS support to its current state.

<a 
href="http://geoserver.org/display/GEOSDOC/4.+WPS+-+Web+Processing+Service";>Read
 more</a> about WPS.

<h3>Unit of Measure</h3>

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 and greatly simplifies 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.  <b>Note</b> that this feature has also been 
backported to the stable 2.0.x branch. Thanks to <a 
href="http://www.swecogroup.com/en/enswecose/";>SWECO</a> for sponsoring the 
backport.

<a 
href="http://docs.geoserver.org/latest/en/user/styling/sld-extensions/uom.html";>Read
 more</a> about UOM support.

<h3>DPI Scaling</h3>

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 <a 
href="http://www.swecogroup.com/en/enswecose/";>SWECO</a> for sponsoring this 
work. <b>Note</b> also that this feature has also been backported to the stable 
2.0.x branch.

<a 
href="http://docs.geoserver.org/latest/en/user/services/wms/vendor.html#format-options";>Read
 more</a> about DPI scaling.

<h3>And More</h3>

And as usual this release comes with a number of bug fixes and minor 
improvements. Check out the entire <a 
href="http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10311&version=15082";>changelog</a>.
 Help us get to 2.1.0 by <a 
href="http://geoserver.org/display/GEOS/GeoServer+2.1-beta1";>downloading</a> 
the beta and trying it out and reporting any issues on the <a 
href="https://lists.sourceforge.net/lists/listinfo/geoserver-users";>mailing 
list</a> or in the <a href="http://jira.codehaus.org/browse/GEOS";>bug 
tracker</a>.

Thanks for using GeoServer!
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to