I’d like to quickly congratulate the uDig developers team for releasing the newest version of uDig.  uDig 1.1 has a venerable history.  Quite a venerable history, as releases go.  In fact, I think uDig might be in line for some kind of Guinness-style award for having the most release candidates (with 14 RCs and even 3 Sanity Checks).  I certainly don’t mean this as a dig (sorry, couldn’t help myself); it just shows that the team wanted to be sure to release a quality product as free of bugs as possible.  That said, the GeoServer team does feel slightly better about our growing number of release candidates (currently at 1.7.0-RC4).  No matter.  uDig is an excellent desktop GIS product and is a great complement to GeoServer.  (I personally have always appreciated its ability to generate SLDs quickly and painlessly.)  Go check it out.

**Update: **I’ve been asked off-camera about uDig’s editing capabilities.  uDig does in fact follow the WFS-T(ransaction) standard, and is one of the best clients out there for doing so.  In this way, one can use uDig to edit features served using GeoServer from the safety of a familiar GUI.  That’s big news (shapefiles and other data structures can be rather opaque to edit otherwise) and I think it merits a mention here.

There are some questions that are asked quite frequently by people who are using GeoServer, or who are thinking about doing so. And certain ones can’t be so easily answered as those in our FAQ. One of the most common I see is this:

_“GeoServer is nifty, but is it fast?” _

Clearly some benchmarks are needed. Testing was first done at a presentation at FOSS4G 2007 by Justin Deolivera (OpenGeo) and Brock Anderson (Refractions Research). They chose to compare performance of GeoServer against MapServer, another popular open-source GIS. The presentation was well-received and showed off the strengths and weaknesses in both servers.

This year, at FOSS4G 2008, Andrea Aime (also OpenGeo) took over the benchmarking process, this time with an updated test suite including thematic mapping, anti-aliasing, raster data, and tile caching. Since the previous year, MapServer had improved its shapefile rendering to be faster than GeoServer’s render time. But Andrea continues:

_“The hard part started when our results showed GeoServer being in the lead in both PostGIS and raster tests. I could buy the PostGIS results, but I did not believe the raster results. MapServer has had long-standing and well-reputed raster support, so how come the newcomer was doing better?” _

Andrea and Justin worked directly with Steve Lime, Paul Ramsey, and Frank Warmerdam to confirm and discuss the findings. But the results were clear: although MapServer was faster at shapefile rendering, GeoServer was faster at raster and PostGIS rendering.

Andrea continues:

_“When you look at our results, remember that the MapServer developers are already working hard to improve MapServer performance, just like they did one year ago with the shapefile results. GeoServer developers won’t be sleeping either, as we’re already working on some changes to get PostGIS support both more secure and faster. _

_For next year, we’re looking forward to doing a joint presentation that will allow each group to tune their respective servers to the best of their capabilities, and look into some extra tests. I’m looking forward to it; a bit of friendly competition is benefiting both servers and keeping the audience interested.” _

Sounds like a friendly throwdown to me.

But don’t just take his word for it.  Why don’t you download the test suite and report back your findings?

Today we have a new release candidate of GeoServer 1.7.x for everyone’s testing pleasure.  We don’t wish to invoke Zeno’s Dichotomy Paradox, but we are in fact very close to the release.  In truth this release candidate only includes six new bug fixes (the most notable regarding projection persistence and Google Earth overlays).  If it seems like we’re going release candidate crazy, rest assured that it is only because we want to ensure that 1.7.0 will be a stable release and not a beta that was rushed out the door.  Give it a try!

Here’s a quick announcement for all those who understand the above.  GeoServer now has an Italian language users mailing list!  Created and moderated by core GeoServer developer Andrea Aime, the mailing list is a resource for those who would like assistance in all things GeoServer, but prefer to discuss in Italian.  This marks the third language for which GeoServer has a mailing list (the second being Portugese).  Subscribe and say ciao!

From the description of the mailing list:

Il gruppo di discussione degli utenti italiani di GeoServer. Potete scrivere per discutere delle funzionalità di GeoServer e ricevere aiuto. Chi volesse partecipare attivamente nello sviluppo di GeoServer è invitato ad utilizzate la maililing list degli sviluppatori (in inglese).

For the past few months, the GeoServer team has been working behind the scenes on rebranding GeoServer.  Historically, GeoServer hasn’t had a very strong visual identity, but there has been significant interest as of late, especially as talk of the new GeoServer UI has entered alpha status.  So, ace stylers Andy Cochran and Chris Patterson worked their design magic and came up with a new icon, logo, and color scheme.  So now we officially unveil the new look of geoserver.org (and this blog)!  This was an iterative process, and the materials benefited from community involvement (specifically the icon, which now happily manages to squeeze in all continents).  Elements of this design will eventually be incorporated into GeoServer itself.  We also have a website which contains icons and logos available for download.  We hope you like the new look as much as we do.

If you’re reading this blog through an RSS feed, why don’t you check out the site itself?