The GeoServer team is pleased to announce the release of GeoServer 2.6.4. Download bundles are provided (bin, war, dmg and exe) along with documentation and extensions.

GeoServer 2.6.4 is a maintenance release of GeoServer recommended for production deployment. This release contains IMPORTANT SECURITY FIXES so please upgrade.

Thanks to everyone who took part by contributing fixes, new functionality, and documentation. Notable changes:

• SECURITY: Fixed a serious vulnerability that allowed arbitrary files on the server to be read by crafting a malicious WFS request

• SECURITY: Fixed a defect that permitted WPS service to continue to respond even when disabled

• Oracle JDBC driver (ojdbc14.jar) is no longer included with the Oracle plugin; ojdbc6.jar or ojdbc7.jar must be obtained from Oracle

• Vendor parameter to specify WMS GetMap interpolation method

• Dynamic raster styling with CQL expression support for color map entries

• User-defined variables in Freemarker templates

• Check the release notes for more details

• This release is made in conjunction with GeoTools 12.4 and GeoWebCache 1.6.2

Thanks to Ben Caradoc-Davies (Transient Software Limited) for this release. Thanks also to Kevin Smith (Boundless) for releasing GeoWebCache 1.6.2 and to Jody Garnett (Boundless) for building the GeoServer 2.6.4 DMG.

About GeoServer 2.6

Articles and resources for GeoServer 2.6 series:

• GeoServer at FOSS4G

  • State of GeoServer and GeoTools 2014 (slides)

• Raster Views in GeoServer via the CoverageView concept (GeoSolutions)

• Advanced Raster Projection in GeoServer (GeoSolutions)

• Supporting Wind Barbs In GeoServer and GeoTools (GeoSolutions)

• GeoServer now supports Vector Footprints for ImageMosaic (GeoSolutions)

• 2.6.3 announcement and change log

• 2.6.2 announcement

• 2.6.1 announcement

• 2.6.0 announcement

• 2.6-RC1 announcement

• 2.6-beta announcement

We are happy to announce the release of GeoServer 2.8-M0. Downloads are available (zip, war, dmg and exe) along with docs and extensions.

This is milestone release of GeoServer made in conjunction with GeoTools 14-M0.

We have both new features and a number of key “under the hood” changes to GeoServer. This technology preview is made available for your evaluation and feedback and is not intended for production.

Highlights from the release notes:

• JAI-Ext integration for geospatial specific image processing operations  (github), adding direct support for NODATA in raster sources

• Replacement of vecmath with EJML matrix library

• Importer improvements, dalwarp/gdal_translate/gdaladdo transformations and ability to add a granule to a mosaic

• Read/write PostGIS curve support

• GetMap support for by layer interpolation methods

• Stop shipping old Oracle JDBC driver

• Pretty print option for style REST API

• Allow environment variables to be used in freemarker template files

Also, looking at the GeoTools 14-M0 release notes, we have:

• Significant increase in GML 3.X encoding speed

• New projections supported: sinusoidal, gnomonic

• New extshape://arrow with parameters controlling its proportions

Thanks to Jody (Boundless) for pulling this release together.

About GeoServer 2.8

GeoServer 2.8 is scheduled for September release. For more information:

• JAI-Ext, the Open Source replacement for Oracle JAI (GeoSolutions)

We will add additional blog posts to this section as news is made available.

The GeoServer team is happy to announce the release of GeoServer 2.7.1. Download bundles are provided (zip, war, dmg and exe)  along with documentation and extensions.

GeoServer 2.7.1 is a stable release of GeoServer recommended for production deployment. Thanks to everyone taking part, submitting fixes and new functionality including:

• Add WMS GetMap support for by layer interpolation methods

• Allow usage of environment variables from various sources in ftl files

• Allow cql expressions in ColorMapEntry for GetLegendGraphic

• This release is made in conjunction with GeoTools 13.1 and GeoWebCache 1.7.1

• For a full list, see the release notes.

Thanks to Kevin (Boundless) and  Torben (Boundless) for this release

The Windows executable installer should now be available.  Sorry about the broken link.

The GeoServer team is happy to announce the release of GeoServer 2.6.3. Download bundles are provided (zip, war, dmg and exe)  along with documentation and extensions.

GeoServer 2.6.3 is a maintenance release of GeoServer recommended for production deployment. Thanks to everyone taking part, submitting fixes and new functionality:

• The WPS download community module is now available on the 2.6.x branch too

• Some WPS fixes related to requests not including the response form

• Fixed layer naming regression that prevented non XML valid names to be used for coverages (care on naming is still advised, different protocols have different requirements, check the ones you are using)

• Some WFS 2.0 join related fixes

• Speed up generation of JSON files when the native CRS is EPSG:900913

• Avoid leaks of commons-httpclient pools (which in turn can lead to a native thread leak)

• Check the release notes for more details

• This release is made in conjunction with GeoTools 12.3

Thanks to Andrea (GeoSolutions), Jody (Boundless) for this release

About GeoServer 2.6

Articles and resources for GeoServer 2.6 series:

• GeoServer at FOSS4G

  • State of GeoServer and GeoTools 2014 (slides)

• Raster Views in GeoServer via the CoverageView concept (GeoSolutions)

• Advanced Raster Projection in GeoServer (GeoSolutions)

• Supporting Wind Barbs In GeoServer and GeoTools (GeoSolutions)

• GeoServer now supports Vector Footprints for ImageMosaic (GeoSolutions)

• 2.6.2 announcement and change log

• 2.6.1 announcement and change log

• 2.6.0 announcement and change log

• 2.6-RC1 announcement and change log

• 2.6-beta announcement and change log

Thanks to some last minute planning, and Boundless renting space, we were able to set aside some time for a code sprint after the FOSS4G-NA conference. One of the goals of this sprint was to onboard new developers to build and run CITE tests. We also had Jim Hughes from GeoMesa joining us as a new GeoServer community member.

Clockwise from the bottom left corner: Torben Barsballe (Boundless), Travis Brundage (Boundless), Kevin Smith (Boundless), Andrea Aime (GeoSolutions)

Offscreen: Jim Hughes (GeoMesa), Jody Garnett (Boundless), Tyler Battle (Boundless)

Andrea introduced us to the OGC Compliance Testing Program (CITE), which provides resources for ensuring conformance with the OGC Standards.

One of the core tools within CITE is the Test, Evaluation, And Measurement (TEAM) Engine, which executes test suites written using the OGC Compliance Test Language (CTL). This is the official test framework of the CITE program, and all CITE tests published by the OGC are written for the TEAM engine, using CTL.

Currently, we execute a number of nightly geoserver builds that run CITE tests:

• cite-wcs-1.0

• cite-wcs-1.1

• cite-wfs-1.0

• cite-wfs-1.1

• cite-wms-1.1

• cite-wms-1.3

These do not encompass the full set of CITE tests published by the OGC. In the interests of adding better test coverage, it is important to familiarize new developers with how the CITE tests are build and run.

During the code sprint, we attempted to set up and execute tests on a local instance of the TEAM engine. This entailed:

• Building the latest GeoServer

• Building the latest TEAM engine

• Building the ets-wfs10 test suite, provided by the OGC

To run the WFS 1.0 CITE tests, we:

• Ran geoserver using citewfs-1.0 data directory

• Ran the TEAM Engine on a local tomcat server

• Configured the WFS test suite in the TEAM engine, and ran it.

There were a few hiccups during this process, but closely following the existing documentation was sufficient to get the CITE tests running properly. While I did not run into this issue, Andrea mentioned that bugs in the CITE tests themselves are about as common as bugs in the OGC-compliant GeoServer services. This makes running CITE tests a bit of a treasure hunt between which test failures are coming from from the tests, and which are coming from the service being tested.

Successful WFS 1.0 CITE Tests!

After I succeed in getting the WFS 1.0 test suite running, I tried building the WCS 1.0 test suite (which was a bit more complicated). I was able to get the tests running, but encountered a number of test failures. Among other things, the WCS CITE tests fail if the endpoint they are querying also publishes WCS 1.1 resources. This means that in order to properly run the tests, you have to build GeoServer without WCS 1.1. There also other test failures that I was unable to debug during the sprint.

Thanks

We would like to thank the GeoServer community for welcoming newcomers, Boundless for renting the space and congratulate Jim Hughes on his new community modules.