Dear Simone:
Thank you for you exhaustive overview of what you are doing.
First I would like to give you a short overview of what I am trying to
accomplish using GeoServer/GeoTools then ask a couple of specific questions
about branches and versions.
Overview of what I am trying to accomplish:
Basically, I want to serve four dimensional (x, y, z and time)
meteorological and oceanographic data that is stored in a proprietary format
as OGC services. My specific objectives are to:
Serve the 4-D data as 2D coverages (WCS) using TIME & ELEVATION
Serve the 4-D data as WMS using TIME & ELEVATION
The new raster symbolization is going to very helpful :-)
Derive vector data from the 2D coverages and serve using WFS
e.g. isopleths, point data for windbarbs, etc.
Server the vector data as WMS using appropriate METOC symbology (e.g.
windbarb)
The new dynamic SLD and graphic objects is going to very helpful
:-)
I want to congratulate the designers/developers of the Dynamic SLD Graphic
objects.
http://geotools.codehaus.org/Dynamic+SLD+Graphic+objects
I found the combination of the MarkFactory with CQL to be very flexible yet
easy to use for implement a new MarkFactory.
Questions about branches and versions:
While your long range goals of "to serve multidimensional cubes through WCS
as well as doing animations for WMS" sounds great, at this time I am only
interested in serving 2D coverages from the 4D data. From your email here
are the two statements that interest me the most:
1) Alex has pointed out it is possible to use Parameters in order to add
TIME, BAND and ELEVATION to serve multidimensional WMS and WCS requests
pretty easily.
2) 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.
If I emulate how Alex added TIME & ELEVATION (#1 above) then how compatible
will that solution be with the version of GeoServer code from #2 above? I
am fine with having to re-factor for a future version of GeoServer if I can
start developing with a branch that allows me work with TIME & ELEVATION
no--I plan on decoupling parameter handling from proprietary data format
handling so only one thin layer should have to be re-factored. As long as
the two solutions are conceptually similar then it shouldn’t be a lot of
work to re-factor for a future version of GeoServer.
Based on both yours and Alex’s response, I think I want to start by
emulating Alex’s solution for TIME & ELEVATION parameters—unless you tell me
this is a "dead end" code path. So, I would like to know which GeoServer
branch Alex used? I see both:
1.7.x_WCS10EMF_ND/
1.7.x_WCS10_EMF/
Also, is there code sample of Alex’s solution for adding the parameters in
Subversion?
Thank you,
Alan
--
View this message in context:
http://www.nabble.com/Re-send%3A-WCS-TIME---ELEVATION-parameters-in-version-1.7--tp19997673p20037580.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
