Kamis, 27 Oktober 2011

Time and elevation support in GeoServer


Busy times in GeoSolutions and in GeoServer land! We just finished adding support for WMS time and elevation in GeoServer WMS on trunk, with plans to backport it to the stable 2.1.x series after the 2.1.1 release.

Configuring and using dimensions is performed, as tradition, by means an easy to use GUI. Just take a layer that has time information (or elevation), like this "storm tracks" layer:


Then switch to the new Dimensions tab and configure time support as follows:

Submit and voilĂ , you have your time enabled layer. Looking at the capabilities you can see GeoServer is automatically extracting the list of values for you (but you could also ask it to return just an interval, for brevity):



If you now ask GeoServer for the WMS layer you'll get only one track, the last one, also known as the current data: 
But then again, you can ask for a month worth of data adding &TIME=2004-08-03/2004-09-03 to your request:
If you really want you also cherry pick the times you want to see, for example with &TIME=2000-08-03T16:00:00.000Z,2000-08-13T16:00:00.000Z,2000-08-17T10:00:00.000Z,2000-08-19T16:00:00.000Z:

For now we're added time and elevation support, but we're getting started with raster data and we should be landing that support soon too.

Interested in multidimensional data management advances? Let us know!

The GeoSolutions team,

Rabu, 12 Oktober 2011

GeoServer News: Hiding layers from the capabilities document

Hi all,
in this blog post we would like to talk about a new functionality that we has just introduced in GeoServer, the layer "advertised" flag.

As you know, ignoring security settings for the moment, all enabled layers configured in GeoServer are made available though all the OGC services for which they make sense: vector layers are published automatically to WMS and WFS, raster layers to WMS and WCS.

This is a fine default behavior, but in some cases one would like that the layer was there, but without making the layer known to the general public. Tipical use cases:
  • you want to expose a set of layers as a layer group, but you don't want to publish the layers separately
  • some application needs to setup a temporary layer, maybe the result of some computation, without having the whole world know about it
  • the administrator wants a layer to be available for testing, but not have the whole world hit it yet (maybe because the layer configuration/styling is not done)
Up until GeoServer 2.1.1 the above was only partially possible by making the layer available only to certain users via the security setup, but in 2.1.2 it got just a lot easier, there is a new publishing flag, "advertised", that you can uncheck to hide the layer:

Once un-ckecked the layer won't appear anymore into the capabilities documents, nor in the layer preview table, but will still be available for all other service requests.

There are other things that could be done to improve layer management, such as attribute renaming, easier association with styles, publishing of a layer only towards certain OGC services and the like. Interested in getting any of that happen today? Let us know!



Regards,
the GeoSolutions Team.