In+ersec+ion for Spatial People

[this story was submitted by a user as a press release (thanks!), I'm republishing it as a story too since it's a pertinent major release]

The GeoServer team is happy to announce the release of GeoServer 2.3.0, available for download.

This release contains six months worth of improvements and fixes to the GeoServer code base. Including several important new features and improvements such as:

• A pluggable configuration subsystem (for the catalog and service configuration)
• GeoWebCache clustering and disk quota improvements
• More powerful layer groups and better control of the WMS capabilities layer tree
• Several security subsystem improvements
• WPS process whitelist (control which processes your WPS is exposing)
• WMS dimensions support improvements (units, custom dimensions)
• JSON and JSONP output format support in many OGC operations
• The monitoring module finally graduating to official extension
• Raster re-projection quality improvements and speedups
• INSPIRE module improvements for the WFS protocol
• A newfound ability to catalogue all components of GeoServer via a REST API

For those daring enough to try out nightly builds the 2.3.x series also offers a new scripting extension allowing you to write WPS processes and small applications in your preferred scripting language. Also included as a nightly community module available is a complete WCS 2.0 service implementation.

More information about the new features of the 2.3.x stream can be found in the  GeoServer 2.3-beta release announcement.

The good news do not stop there. GeoServer has finally completed the OSGeo incubation and it’s now an official OSGeo project. Many thanks to all that participated, in particular Jody Garnett for constantly pushing forward, Landon Blake for mentoring us, and all the people that participated to the FOSS4G-AU code sprint in which all of the grunt work of provenance review was done. We want to thank in particular Jody Garnett, Adam Brown, Karin Stronkhorst, Luca Morandini and Joshua Vote for the hard work.

And last but not least there have been some bug fixes since the RC1 release, you can find a full list in the GeoServer 2.3.0 changelog. Included in this list, for those willing to try out nightly builds, is a new fast WMS JPEG encoder based on libjpeg-turbo which should give a nice boost to your raster data serving.

Download GeoServer 2.3, try it out, and provide feedback on the GeoServer mailing list.  As with any new version, be sure to backup your data directory before upgrading.

Thanks again for using GeoServer!

Download GeoServer 2.3

The GeoServer team is happy to announce the release of GeoServer 2.3.0, available for download.

This release contains six months worth of improvements and fixes to the GeoServer code base. Including several important new features and improvements such as:

• A pluggable configuration subsystem (for the catalog and service configuration)
• GeoWebCache clustering and disk quota improvements
• More powerful layer groups and better control of the WMS capabilities layer tree
• Several security subsystem improvements
• WPS process whitelist (control which processes your WPS is exposing)
• WMS dimensions support improvements (units, custom dimensions)
• JSON and JSONP output format support in many OGC operations
• The monitoring module finally graduating to official extension
• Raster re-projection quality improvements and speedups
• INSPIRE module improvements for the WFS protocol
• A newfound ability to catalogue all components of GeoServer via a REST API

For those daring enough to try out nightly builds the 2.3.x series also offers a new scripting extension allowing you to write WPS processes and small applications in your preferred scripting language. Also included as a nightly community module available is a complete WCS 2.0 service implementation.

More information about the new features of the 2.3.x stream can be found in the  GeoServer 2.3-beta release announcement.

The good news do not stop there. GeoServer has finally completed the OSGeo incubation and it’s now an official OSGeo project. Many thanks to all that participated, in particular Jody Garnett for constantly pushing forward, Landon Blake for mentoring us, and all the people that participated to the FOSS4G-AU code sprint in which all of the grunt work of provenance review was done. We want to thank in particular Jody Garnett, Adam Brown, Karin Stronkhorst, Luca Morandini and Joshua Vote for the hard work.

And last but not least there have been some bug fixes since the RC1 release, you can find a full list in the GeoServer 2.3.0 changelog. Included in this list, for those willing to try out nightly builds, is a new fast WMS JPEG encoder based on libjpeg-turbo which should give a nice boost to your raster data serving.

Download GeoServer 2.3, try it out, and provide feedback on the GeoServer mailing list.  As with any new version, be sure to backup your data directory before upgrading.

Thanks again for using GeoServer!

Download GeoServer 2.3

The GeoTools community is pleased to announce the availability of GeoTools 8.6 for download from source forge:

• geotools-8.6-bin.zip
• geotools-8.6-doc.zip
• geotools-8.6-userguide.zip
• geotools-8.6-project.zip

This release is also deployed to the OSGeo Maven Repository. For more information on setting up your project with Maven consult the Quickstart.

About GeoTools 8.6
This is a bug fix release containing fixes and improvements, including:

• Several fixes in the WFS client, making it work against TinyOWS and ArcGIS WFS server
• Improvements in usage of filter fuctions from SLD (some functions did not properly convert their arguments from string to numeric)
• Removed tiling artifacts when rendering oversampled grid coverages
• Sped up the usage of FIDFilter objects in map rendering

Full details are available in Jira's release notes.

Upgrading from GeoTools 2.7

For those migrating from GeoTools 2.7, upgrade instructions are available. No additional GeoTools 2.7 released are scheduled. Thanks for using GeoTools, and Enjoy!
The GeoTools Community
http://geotools.org

The GeoServer team is happy to announce the release of GeoServer 2.2.4, now available for download.

This is the latest release of the stable 2.2 series. The changes that might interest the most users are:

• the monitoring extension module just got promoted to official extension [GEOS-5538]
• the status page does not throw errors after catalog reloads anymore [GEOS-5371]
• one critical fix in the REST configuration of freemarker templates [GEOS-5533]

The changelog also contains the following minor bug fixes

• [GEOS-5338] – Filter function IEEERemainder mishbehaves in SLD
• [GEOS-5537] – Tiling artifacts with RasterSymbolizer using bilinear interpolation (when oversampling raster)
• [GEOS-5551] – WFS 1.0 capabilities will NPE with misconfigured OGR and XSLT output formats
• [GEOS-5565] – workspace admin unable to create sql view
• [GEOS-5570] – QueryProcess fails if called with an OGC filter (either 1.0 or 1.1)
• [GEOS-5197] – Use the layer abstract as the GeoRSS channel description
• [GEOS-5561] – Missing i18n support for ReprojectPage
• [GEOS-5562] – Missing i18n support for WorkspaceEditPage
• [GEOS-5563] – slight mixed up order of Y-parameters in AffineTransformPanel

Also, looking at the corresponding GeoTools release changelog we have the following extra goodies in:

• improvements in the WFS cascading, we can now better interact with remote WFS servers running on TinyOWS and ArcGIS
• imageio-ext was upgraded to version 1.1.6, which means from now on GeoServer uses GDAL 1.9 to extends the range of raster formats it supports

Download GeoServer 2.2.4, try it out, and provide feedback on the GeoServer mailing list.

Thanks again for using GeoServer!

The GeoServer team is happy to announce the release of GeoServer 2.2.3, now available for download.

This is the latest release of the stable 2.2 series and contains some small new features and interesting fixes:

• [GEOS-3885] – Update Freemarker templates through REST API
• [GEOS-5325] – Add title and abstract to LayerGroupInfo
• [GEOS-5462] – The rendering thread can block forever under request cancellation
• [GEOS-5479] – Error in Documentation: </PropertyName> tag used instead of </Literal>
• [GEOS-5483] – json output in WPS extension does not work due to missing library
• [GEOS-5485] – Border artifacts when reprojecting single banded (scientific) raster data

Also, looking at the corresponding GeoTools release changelog we have the following extra goodies in:

• better support for chaining rendering transformations
• fixes to time/date handling in CQL
• Oracle specific SDO_NN function to find the N nearest objects to a given location

We also welcome our newest committer, Davide Savazzi, and thank him for the work on Freemarker template through the REST API and the title and abstract support in layer groups, as well as the SDO_NN work back in GeoTools.

Download GeoServer 2.2.3, try it out, and provide feedback on the GeoServer mailing list.

The GeoServer team is happy to announce the release of GeoServer 2.2-RC3.The release is available for download from:

http://geoserver.org/display/GEOS/GeoServer+2.2-RC3

This release comes with assorted bug fixes and small improvements, and aims to be the latest RC before the final release. Notable changes:

• improvements in the security subsystem upgrade from the 2.1.x series
• bug fixes and improvements in the control-flow module (you won’t be wondering anymore if it’s properly installed, or not)
• avoid deadlocks on some WFS transactions

The entire change logfor the 2.2-RC3 release is available in the issue tracker:

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10311&version=18700

A very special thanks to all those who contributed bug fixes and improvementsto this release.

–The GeoServer Team

Here's the recent open source geospatial news in batch mode, which includes everything about FOSS4G 2011 on the geoblogs that we haven't mentioned yet.

On the FOSS4G 2011 Conference front:

• Interesting numbers, "By 2011 there are now 19,471 unique subscribers to OSGeo, more than 400 mailing lists, and more than 15 million lines of code, with 740 contributors, and 269 that have contributed for more than 12 months."
• Slashgeo editor Nicolas summarized Brian Timoney's excellent talk at FOSS4G 2011, and if you want to hear it yourself, here is that 14-minutes impassioned talk on the state of the geospatial industry, Brian demonstrate how much better we could do
• Here's the slides of Paul Ramsey's keynote
• Here's Jody Garnett's updated slides on the WPS Shootout
• Here's the entry to read about Open Source and Open Data at the U.K. Ordnance Survey
• If you haven't read too much about it already, here's an entry on the case study of the U.S. FCC National Broadband Map based on open source geospatial software
• Here's the what's coming to PostGIS 2.0 slides [pdf]
• I heard comments that 30-minutes talks at FOSS4G 2011 was too short for the presenters to dive into their subjects, would you agree? If you're interested in what could be improved see this recap of FOSS4G 2011 by OSGeo's president
• Here's Directions Mag complete wrap up of the conference

In other news:

• I was surprised to read that Tyler Mitchell won't be the OSGeo Executive Director anymore
• GWT-OpenLayers version 0.6 has been released, that's the wrapper library for using OpenLayers in Google Web Toolkit applications
• MapFish is now an official OSGeo project
• This entry reminds us of the comprehensive list of web mapping toolkits (there's too much of them!)
• SS mentioned GrassrootsMapping.org, which is a crowdsourcing aerial image project with goals similar to OpenAerialMap.org

This year at the FOSS4G the WPS Shootout was introduced and presented some of the conformance / interoperability results, which PyWPS was the most interoperable, as well the ZOO project, while GeoServer had a poor client support. The performance of each WPS software was not evaluated, but with the WMS Shootout coming in this Friday afternoon, the domain of map tiling or Web Map Tile Service (WMTS) could be another standard to be evaluated at the FOSS4G. With so many products now in the market for map tiling, such as MapCache, Tilecache, Mapnik, TileMill, GeoWebCache, MapProxy, I think it might be a good idea to form a WMTS Shootout. It could validate the tiles generation process, the interoperability with clients and the performance on delivering the tiles to the client (ex. OpenLayers) as well as features offered (e.g. reprojection on-the-fly, etc.).