Dear Smith,
apologies for the late answer, and apologies in advance if the answer
will be long. :-).
We have been working since the beginning of this year (well actually a
earlier than that..) towards allowing multidmensional file formats
like HFD4, netCDF-CF, GriB1 and HDF-EOS (we are lokking at HDF5 for
cosmo-skymed just now..) to be served through the GeoServer.
Baseline goal is to be able to get "d layers out of multidimensional
sources, while the more ambitious goal is to be able to serve multidim
cubes through WCS as well as doing animations for WMS. This was for
the background.
Now the directions as well as the work done.
To achieve all this we have identified a a few areas to work on:
1> Allowing GeoServer to correctly parse the various multidim related
params like TIME, BAND, etc.
This has been implemented as part of GSIP 24. That work is actually
sitting on a branch, since we are waiting for 1.7.0 to be released in
order to merge it onto 1.7.x and trunk.
Notice that this work will only allow GeoServer to actually parse the
parameters in incoming requests, this does not involve actually
passing them to the underlying plugin.
2A> Allowing current GridCoverage plugins to actually use the new parameters.
The current GridCoverage I/O mechanism has a few limitations which
have been inherited from the GridCoverage GCE specification.
However as Alex has pointed out it is possible to use Parameters in
order to add TIME, BAND and ELEVATION to serve multidim WMS and WCS
requests pretty easiliy. As far as the assumption to have 1 coverage
for each file that can be overcome (we have done that for HDF4) same
applies to the claime impossibility to use a DBMS backed (there is a
new imagemosaic-jdbc plugin available).
This means that once GSIP 24 will be committed, it will actually be
decently easy to extract 2D slices from multidimensional source, we
will just have to agree on the Parameter semantic and add the wiring
code to the GeoServer which would forward requests down under to the
coverage plugins.
I was actually discussing this with Daniele since we have a few
plugins for HDF4 which are pretty much ready to go (they are able to
serve data as processed using APS and or TERASCAN sotware).
2B>Refactor CoverageIO and move towards GeoServer ND.
As I said above the current GridCoverage I/O framework has a few
limitations, hence in order to fully support multidimensional coverage
source we started with defining a new API for it, and we are
completely refactoring the internal of the GeoServer to support this
new API. This is an ongoing work and there is not muc documentation.
We have ported the old GeoTiff code to this new API, but our main goal
is to have an initial version for the end of the year which should be
able to server netCDF-CF, GriB1, and a few HDF sources as explained
above. We have more ambitious goal for next year, gor this email is
getting long enough already :-).
This work is now based on GeoServer 1.7.x + gsip 24 + new Coverage API
and lives in its won branch, however we should upgrade it and make it
work against GeoServer trunk in early november, since this work will
not be backported to 1.7.x since it contains so many differences. This
work should lay down the basis for future versions of GeoServer
coverage support as well as for the "ambitious" part I talked about
before.
Conclusion.
I just tried to give a (quick) and (I hope) exhaustive overview of
what we are doing, in order to trigger a discussion which wouold be
tailored to your goals.
Regards,
Simone.
On Wed, Oct 15, 2008 at 6:00 PM, Smith, Alan G. <ALAN.G.SMITH@anonymised.com> wrote:
I originally sent this on 7 Oct 2008 with no response. I would be grateful
for a quick answer to the first question below.
________________________________
From: Smith, Alan G.
Sent: Tue 10/7/2008 12:49 PM
To: geoserver-devel@lists.sourceforge.net
Subject: WCS TIME & ELEVATION parameters in version 1.7?
GeoServer Developers:
In GeoServer version 1.7, are the WCS TIME & ELEVATION parameters going to
be supported as indicated by GSIP 24?
http://geoserver.org/display/GEOS/GSIP+24+-+TIME-ELEVATION-BAND+parameters+parsing+for+WMS+1.1.1+WCS+1.X
If yes, do you have any sample code for a GeoTools coverage plug-in that
uses the WCS TIME & ELEVATION parameters? I have checked out version
1.7-RC3 and have inspected some of the code for the EMF bindings, but I
could not find an example of a plug-in that uses the EMF bindings--not that
I have any real experience with EMF bindings.
My objective is to develop is to develop a GeoTools coverage plug-in for a
proprietary data format where there are 2D coverages that vary in time and
elevation, and I would like to only register one coverage store and coverage
per data parameter using time and elevation to select the individual 2D
coverages.
Thank you,
Alan Smith
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
-------------------------------------------------------
Eng. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928
http://www.geo-solutions.it
http://www.geo-solutions.it/simone.giannecchini
http://www.linkedin.com/in/simonegiannecchini
-------------------------------------------------------
