GeoServer Blog

GeoServer 1.5.0 Released

The GeoServer Project is proud to announce the release of version 1.5.0. This release turns GeoServer in to a complete solution for serving any type of spatial data, as the primary focus has been support for raster formats, starting with GeoTiff, ArcGrid, World Images, GTOPO30, and image mosiacs and pyramids. As always GeoServer is focused on open standards and open data, making the rasters available as a Web Map Service, but also through the Web Coverage Service specification, which gives full access to the raw data, not just the final image. The WCS passes all OGC Compliance tests, and will be fully certified very soon. Other notable improvements for this release include easier adding of data through the web admin tools, better support for Google Earth KML, performance and scalability improvements, and as always a heap of bug fixes. The release can be found here.

The Web Coverage Service implementation and WMS raster support have been the result of work carried out by GeoSolutions, who have been a prominent member of the GeoServer community for some time. The community is glad to take this contribution and make it part of the GeoServer core and thanks GeoSolutions for their excellent work. It is amazing to see not just bug fixes and new data formats, but completely new functionality that would not be possible without the ever expanding community.

This is an exciting time for GeoServer. As we look to the future there are more interesting developments on the horizon. Among them include Versioning WFS, a full implementation of WFS 1.1, multi-dimensional raster data through the WCS, and support for security and authentication. Also expect to keep seeing improvements to performance and scalability, better support for KML, and a variety of other neat and interesting features.

Read More

Translators Apply Here

As we get closer and closer to GeoServer 1.5.0 it is time to make sure that our translations are up to date. Currently GeoServer maintains translations for the French, German, Spanish, and Japanese languages. We have been able to so with kind contributions from our users. And we are always looking to expand in order to support new languages.

So… are you a GeoServer user whose native tongue is not English or one the languages listed above? Are you looking to get more involved in the GeoServer project? Well what better way to so then to become a translation maintainer. Heck, its the easiest way to obtain commit status without writing any code :).

If interested please do not hesitate to post a message to the users list and let us know. The Translation Guide details the process of maintaining a translation and what you will be getting yourself into. Any contributions will be much appreciated by all of us in the GeoServer community.

Read More

Help us test 1.5.0-RC3!

The GeoServer team has been working away trying to get things ready for our completely stable 1.5.0 release. We’re crossing our fingers that this is the final release candidate, but we want to make sure it’s incredibly solid. So you can help us out a ton by downloading the release and reporting any and all problems. Even small ones, even documentation being a bit off. As we really want to get this out the door we promise that most any real new bug reported will be dealt with incredibly fast.

There have been a number of fixes for this release, we greatly improved error reporting in the GUI with regards to setting up files (shapefiles and rasters), and added a ‘directory datastore’ for easier management.  The two of these greatly improve the work flow for the most common data adding operations.  We’ll try to get the documentation on using this new feature up to date soon, but it should be pretty obvious from the gui. A bug with rotation in image files was fixed, along with multi geometries in in-line features. PostGIS also now has an option to use ‘estimated extents’, for those with huge datasets. And a ‘reflector’ was added to allow defaults for WMS requests, more docs on that soon as well. Also improved were SLD parsing, date handling and logging. If you want to get to the nitty gritty of the bug fixes, the full change log is available.

I personally am really excited about this coming 1.5.0 release, it feels really solid, has a lot of great new code, and really represents a (first) culmination of all the hard work that the Geo-Solutions guys have put in. It’s great to see GeoServer grow in to an even more diverse community. It’s a challenge to deal with all the incoming code at once, but one of those ‘good’ challenges that means there are just lots of big new features coming our way. Look for an Ingestion Engine, WFS versioning, 4d+ Coverages, Complex Features, better Google Earth support, a new UI, and WFS 1.1 all coming online pretty soon. It’s an exciting time.  Shoot, that reminds me, I probably should update the road map again.  I just can’t keep up with all this great work.

Read More

The 37 gigabyte GML file

As GeoServer matures one of the main focuses becomes the ability to scale - dealing with both large amounts of data and large amounts of users. I got a bit of time to play with GeoServer a week or so ago, and wanted to test out a bit of the large data side of things. On our geoserver demo site, we’ve got about 19 gigabytes of data that we’re serving up. It’s all available through the WMS with OpenLayers on the front end, but the data is never exposed all at once. One of GeoServer’s strengths is the WFS, which provides access to the raw vector data, so I wanted to try to download the whole dataset.

GeoServer has some great fundamental design, as its built in such a way that data is never really held in memory, it streams from the database in to GeoTools java objects and then out to the appropriate output format. So in theory we should be able to stream GML from databases of any size. So that’s what I did, and there were absolutely no memory errors or other problems. Due to the verbose nature of GML the file GeoServer produced was about 37 gigabytes - containing road, landmark, and water data for the whole US, and country boundaries and place names for the world. The data was came down at 4.97 MB/s, which I don’t think is too bad for transforming it to GML on the fly. One interesting thing I noticed that with larger datasets there’s a noticeable pause before the data starts returning. With small datasets the streaming nature of GeoServer tends to produce results right away. So we’ll have to do some investigation to see what’s taking that time - hopefully it’s something we have control over and not buried in PostGIS or some such. I do believe that GeoServer can handle databases of any size, and would love to hear reports from people out there working with even bigger sets of data.

In the next couple weeks we’re also going to have Justin set up a better testing suite for scalability, using JMeter. A number of people have done testing against GeoServer with it before, but in a more ad hoc way. This will build the tests in to the source distribution, so that we are sure it gets run with every release, so we don’t have any regressions. There have been many speed improvements of late, and many more to come, so we want to be sure that other changes in the code don’t accidentally affect things. One more tidbit of scalability news, Gabriel reported that he attended a meeting where someone reported some GeoServer benchmarks, successfully supporting 1000 requests.

Read More

GeoServer 1.5.0-RC2 released

The GeoServer team is proud to announce the second release candidate for the 1.5 series. This release brings us closer to the stable 1.5.0 release of GeoServer that contains the new and exciting coverage support (WCS). To compliment the release we have created more documentation and tutorials, along with some tools to help you process your raster images.

You can download the latest version here.

Changes in this version include:

  • Bug fixes
  • Kml returns proper PNG files
  • Kml strips out illegal characters now
  • Improved error messages
  • UI improvements
  • Inline features are back
  • Links to old homepage updated
  • Performance optimization

The full changelog for this release can be found here.

Read More