GeoServer 2.0.2 release

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.

As previously mentioned, GeoServer now provides support for Oracle Georaster, custom database layouts for image data and polymorphism.

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.

6 Comments

  1. Posted May 26, 2010 at 7:53 pm | Permalink

    I love the new area of validity feature. How is it calculated?

  2. Posted June 1, 2010 at 11:02 pm | Permalink

    There are some really great new features in this release – well done!

  3. Posted June 2, 2010 at 2:41 pm | Permalink

    The area of validity comes straight from the official EPSG database. It’s not calculated, it’s declared.
    For example, take 32632, it’s an UTM 32N projection, its area of validity is set to those values to ensure the deformation error introduced by the projection never goes above 20m, so that representations at 1:100.000 are valid, which means, as far as I know, that the allowed error in the printed representation, 0.2mm, is higher than the error introduced by the projection itself.
    So, you see, it’s a matter of convention, if UTM were designed for valid representations at 1:10.000 the area of validity would be smaller.

  4. Yingqi Tang
    Posted June 7, 2010 at 10:52 am | Permalink

    Is the new area of validity feature just for demo purpose? Is there an interface like WMS or so for user to request that area in a map or a vector feature?

  5. Posted June 29, 2010 at 6:13 am | Permalink

    hi,, i the undersigned Sujay Chokshi.. jus want to knw that why i m nt able to run my sld files in 2.0.2 from 2.0.1…

    or what chages i have to take care..???

    rply as well as possible

  6. Victor Tey
    Posted July 8, 2010 at 9:05 pm | Permalink

    Try the mailing list sujay, you will get better responses from the community there 🙂

Download GeoServer