<div style="margin: 0px 2px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="margin: 0px 1px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="padding: 4px; background-color: #c3d9ff;"><h3 style="margin:0px 3px;font-family:sans-serif">Sent to you by Hugo Martins via Google Reader:</h3></div>
<div style="margin: 0px 1px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="margin: 0px 2px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="font-family:sans-serif;overflow:auto;width:100%;margin: 0px 10px"><h2 style="margin: 0.25em 0 0 0"><div class=""><a href="http://blog.geoserver.org/2010/09/04/geoserver-21-beta-released/">GeoServer 2.1 Beta Released!</a></div></h2>
<div style="margin-bottom: 0.5em">via <a href="http://blog.geoserver.org" class="f">GeoServer Blog</a> by Justin Deoliveira on 9/4/10</div><br style="display:none">
<p>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.</p>
<h3>WMS Cascading</h3>
<p>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 <a href="http://www.unipg.it/">University of Perugia</a> for sponsoring this feature.</p>
<p><a href="http://geoserver.org/display/GEOS/GSIP+47+-+WMS+cascading">Read more</a> about WMS cascading.</p>
<h3>Virtual Services</h3>
<p>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.</p>
<p>Special thanks to <a href="http://www.landgate.wa.gov.au">Landgate</a> for funding this work.</p>
<p><a href="http://docs.geoserver.org/latest/en/user/services/virtual-services.html">Read more</a> about virtual services.</p>
<h3>Layers from SQL</h3>
<p>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. </p>
<p>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. </p>
<p>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.</p>
<p><a href="http://gridlock.openplans.org/geoserver/trunk/doc/en/user/data/sqlview.html">Read more</a> about SQL layers.</p>
<h3>WPS</h3>
<p>With 2.1 and the arrival of WPS we welcome a new OGC service to the family. The <a href="http://www.opengeospatial.org/standards/wps">Web Processing Service</a> 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. </p>
<p>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.</p>
<p>Thanks to <a href="http://www.refractions.net/">Refractions Research</a> 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.</p>
<p><a href="http://geoserver.org/display/GEOSDOC/4.+WPS+-+Web+Processing+Service">Read more</a> about WPS. <a href="http://sourceforge.net/projects/geoserver/files/GeoServer%20Extensions/2.1-beta1/geoserver-2.1-beta1-wps-plugin.zip/download">Download</a> the WPS extension now to try it out.</p>
<h3>Unit of Measure</h3>
<p>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. </p>
<p>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> and <a href="http://www.malmo.se/">Malmö City of Sweden</a> for sponsoring the backport.</p>
<p><a href="http://docs.geoserver.org/latest/en/user/styling/sld-extensions/uom.html">Read more</a> about UOM support.</p>
<h3>DPI Scaling</h3>
<p>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. </p>
<p>Special thanks again to <a href="http://www.swecogroup.com/en/enswecose/">SWECO</a> and to <a href="http://www.malmo.se/">Malmö City of Sweden</a> for sponsoring this work. <b>Note</b> also that this feature has also been backported to the stable 2.0.x branch.</p>
<p><a href="http://docs.geoserver.org/latest/en/user/services/wms/vendor.html#format-options">Read more</a> about DPI scaling.</p>
<h3>And More</h3>
<p>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. Be sure to report 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>.</p>
<p>Thanks for using GeoServer!</p></div>
<br>
<div style="margin: 0px 2px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="margin: 0px 1px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="padding: 4px; background-color: #c3d9ff;"><h3 style="margin:0px 3px;font-family:sans-serif">Things you can do from here:</h3>
<ul style="font-family:sans-serif"><li><a href="http://www.google.com/reader/view/feed%2Fhttp%3A%2F%2Fblog.geoserver.org%2Ffeed%2F?source=email">Subscribe to GeoServer Blog</a> using <b>Google Reader</b></li>
<li><a href="http://www.google.com/reader/?source=email">Get started using Google Reader</a> to easily keep up with <b>all your favorite sites</b></li></ul></div>
<div style="margin: 0px 1px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>
<div style="margin: 0px 2px; padding-top: 1px; background-color: #c3d9ff; font-size: 1px !important; line-height: 0px !important;"> </div>