GeoWebCache 0.7.1 is out on SourceForge. There was an issue with the WAR file, so the release has been bumped by .1 since last night. The actual code diff to 0.6.0 is 3746 lines (excluding openlayers and the formatter.xml), so there is a substantial number of changes under the hood. One of the main things is that layers now have a grid parameter and a bounding box. The grid should be the maximum extent of the coordinate system and is used to calculate the internal grid, and which is directly reflected in the cache keys. Separating these two means that you can later expand or reduce the bounds of the layer, and cached tiles will still work.

Other changes include:

• Support for multiple WMS backends per layer, queried in round robin fashion with automatic failover

• Microsoft Virtual Earth tiling support

• Google Maps tiling support

• Improved handling of layer bounds, give a rough estimate and it will approximate to closest metatile for all zoom levels

• Ability to run Jetty directly in Eclipse

• Some code cleanup, using GeoTools coding standard now (almost)

• Reduced JCS dependecies (berkeleydb,hsqldb,mysql), thereby cutting download in half

• Included configuration files and OpenLayers clients for topp:states, for testing

• Various bugfixes

The keen observer will note that this has very little to do with the features originally scheduled for 0.7, but it’s a lot of improvements nonetheless. Please make sure to revisit the configuration notes in the wiki since a number of things, including names of configuration parameters, have changed.

I have noticed that a number of people have reported problems with data in SRSs different from EPSG:4326 and EPSG:900913. Note that the the WMS Tiling Recommendations do not cover other reference systems, but we would be happy to look at them if you supply data and a little bit of your time.

Looking ahead we want to branch out in two separate directions. On one hand we want to integrate more tightly with GeoServer, which was originally planned for this release, on the other hand there appears to be demand to support other backends than WMS. While these are in no way mutually exclusive, supporting other backends would require some internal rewiring (Andrea Aime has suggested the Spring framework, which is also used in GeoServer and in many other high profile projects). Feel free to voice your opinion, especially if you are inclined to contribute in one way or the other.

QA is also becoming a serious concern at this point. Version 0.7.1 includes 18 unit tests that exercise the internal grid / metatiling system a fair bit, and it includes configuration files and OpenLayer clients for testing topp:states (loaded from a remote server) with EPSG:900913 and EPSG:4326. This is not enough, other parts of the system require additional tests, and functional ones to test the package as a whole, but it’s a start.

Thanks to everyone who has contributed patches and feedback, I look forward to hearing from you.

GeoServer 1.6.2 is now available for download here. This is a Security Release, which means it contains fixes for two Security Vulnerabilities. We highly recommend that you upgrade to this version. We found out about both these vulnerabilities in the past couple days, and made an effort to fix them and get this release out as quickly as possible. One of the issues also affects older versions of GeoServer. We are not doing a security release for it at this time for all the older versions, but have clear instructions on how to update one file to disable the page where the exploit is possible. We highly recommend that any production instances of GeoServer follow this, it should be easier to do than a full upgrade.

The GeoServer team announces the release of GeoServer version 1.6.1! Here are some of the highlights in this release:

GeoServer now supports FeatureType aliases, which allows for the creating of friendly names for unwieldy FeatureTypes. Also, support has been added for limiting (per FeatureType) the maximum number of features that can be requested by a client, thus easing server load. (Thanks to Landgate for funding both of the above!). Cédric Briançon from Geomatys contributed the GetFeatureInfo operation on WMS coverage data, and GeoServer can now output PDFs from raster as well as vector data. Saul Farber of MassGIS added support for UpdateSequence, which returns a “revision number” of the capabilities of the service; this gives clients more efficient access to the Capabilities document. Also, there have been improvements in MySQL integration: The Java connector was updated, performance was improved, and GeoServer is now using the more-efficient Well Known Binary protocol.

In total, this new release contains over 40 patches and improvements since 1.6.0. (You can view the changelog for details. You can download this latest version from geoserver.org. As usual, we thank everyone who has tested out the software and reported issues. Please continue to submit bug reports using our bug tracker.

Early this year I submitted an article to GIS Development and it got published in the February issue!! You can check out the article here. Let us know what you think.

Since I have been the intern at The Open Planning Project for a couple of months, I think that its about time I introduce myself and what I have been up to. First the introductions. I am Ivan Willig, an undergrad at College of the Atlantic and currently studying urban planning. Now to my work. As some of you might know (if you read this blog) Tim Coulter and Sebastian Benthall have doing some excellent work with GeoServer, Versioning WFS and OpenLayers. The software uses versioning to allow shared editing and viewing history of edits. I have taken their work and applied it to make a new GeoServer user’s map. You may remember the old map, kind of slow and hard to use. I hope that ease of use of the new GeoServer user’s map will encourage all you GeoServer people to post. You will find the GeoServer user’s map at http://sigma.openplans.org/users/. It should be fairly self-explanatory, however if you have any questions let me know at iwillig [at] openplans.org.

You might also notice that user’s map is using nicer styles for the Tiger dataset on Sigma. Tiger is the US Census data set that has high quality data for the whole United States, road, water-bodies… etc. This was the other part of my work at TOPP, redoing the styles for the Tiger dataset. I am building off the work done by Arne Kepp and Portland’s TriMet.

To find out more about integrating GeoServer and Tiger information please visit the GeoServer wiki http://geoserver.org/display/GEOSDOC/Loading+TIGER+data.

Vmap is a similar dataset, produced by the Department of Defense, but covering the whole world. Check out this tutorial out for more info. http://docs.codehaus.org/display/GEOSDOC/Loading+VMAP0+data .