Hello all,
How can we specify irregular depth values using WCS spec?
E.g.(in metres) 5,30, 50, 100, 200, 400
Cheers,
adit
Ciao Adit,
could you please be a bit more specific? Are you talking about a
describ coverage or what?
Simone.
On 8/10/06, Adit Santokhee <ads@anonymised.com> wrote:
Hello all,
How can we specify irregular depth values using WCS spec?
E.g.(in metres) 5,30, 50, 100, 200, 400
Cheers,
adit
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions
-------------------------------------------------------
Hi Simone,
It is actually for a describe coverage operation. Suppose Ive got a 4D
coverage with depth values at irregular intervals. How am I going to
represent the depth values?
Cheers,
Adit
-----Original Message-----
From: Simone Giannecchini [mailto:simboss1@anonymised.com]
Sent: 10 August 2006 14:53
To: Adit Santokhee
Cc: geoserver-devel@lists.sourceforge.net;
geotools-devel@lists.sourceforge.net
Subject: Re: [Geotools-devel] irregular depth values
Ciao Adit,
could you please be a bit more specific? Are you talking about a
describ coverage or what?
Simone.
On 8/10/06, Adit Santokhee <ads@anonymised.com> wrote:
Hello all,
How can we specify irregular depth values using WCS spec?
E.g.(in metres) 5,30, 50, 100, 200, 400
Cheers,
adit
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions
-------------------------------------------------------
Quick answer before I dig a bit.
You have multiple ways to describe a coverage and somehow this is confusing.
At the very bottom line I would just used
a 3D envelope using the extremes of the spatial cube your data covers.
In this way you just forget about the data itself is organized.
If you want to describe a bit more in detail the structure of your
coverage, you need to make use of the grid element as describe here
below:
http://schemas.stylusstudio.com/opengis/n9b256d84/complexType_RectifiedGridType_1.html
http://schemas.stylusstudio.com/opengis/n9b256d84/complexType_GridType_1.html
There are various thing to point out.
- You need to provide at least a 3Denvelope.
- You can use the rectified grid element only if you have a regularly
spaced grid (which is not your case) which means that there is an
affine transformation between the internal cartesian grid crs and
between the coordinates of a projected or geographic coordinate
reference system.
- The other option is to use the grid element which is basically for
unrectified grids. Quoting the link above "Implicitly defines an
unrectified grid, which is a network composed of two or more sets of
equally spaced parallel lines in which the members of each set
intersect the members of the other sets at right angles. "
Using this element along with an envelope you could basically specify
something like:
"I have some data in the spatial region bounded by this envelope whose
internal structure is as specified by the grid"
In terms of GML/XML for the grid, I would do as follows:
<gml:Grid dimension="3">
<gml:limits>
<gml:GridEnvelope>
<gml:low>0 0 0</gml:low>
<gml:high>200 300 10</gml:high>
</gml:GridEnvelope>
</gml:limits>
<gml:axisName>lon</gml:axisName>
<gml:axisName>lat</gml:axisName>
<gml:axisName>elev</gml:axisName>
</gml:RectifiedGrid>
With this you would be saying that, inside the envelope you also
provide, you have a non regular grid where each 2d layer is of 200*300
and where you have 10 differetn levels. I think I could come up with
something more complex in case you ask in order to be able to list
exactly your layers, but the wholepoint is WCS 1.0 has not been
designed having in mind non regular grid (as Adnrew Woolf pointed out
in one of his documents).
Hope that helps.
Simone.
On 8/10/06, Adit Santokhee <ads@anonymised.com> wrote:
Hi Simone,
It is actually for a describe coverage operation. Suppose Ive got a 4D
coverage with depth values at irregular intervals. How am I going to
represent the depth values?Cheers,
Adit
-----Original Message-----
From: Simone Giannecchini [mailto:simboss1@anonymised.com]
Sent: 10 August 2006 14:53
To: Adit Santokhee
Cc: geoserver-devel@lists.sourceforge.net;
geotools-devel@lists.sourceforge.net
Subject: Re: [Geotools-devel] irregular depth valuesCiao Adit,
could you please be a bit more specific? Are you talking about a
describ coverage or what?Simone.
On 8/10/06, Adit Santokhee <ads@anonymised.com> wrote:
>
> Hello all,
>
> How can we specify irregular depth values using WCS spec?
>
> E.g.(in metres) 5,30, 50, 100, 200, 400
>
> Cheers,
>
> adit
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> Geotools-devel mailing list
> Geotools-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions-------------------------------------------------------
--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions
-------------------------------------------------------
On 8/10/06, Adit Santokhee <ads@anonymised.com> wrote:
Hi Simone,
It is actually for a describe coverage operation. Suppose Ive got a 4D
coverage with depth values at irregular intervals. How am I going to
represent the depth values?
Hi Adit:
We have a similar situation with presenting different atmospheric
pressure levels for meteorological forecast. In particular, certain
pressure level will vary in height over the continent, and the height
is expected to change with time. For now with our WMS viewer the
variance in height is depicted as just another coverage.
Alex
Cheers,
Adit
-----Original Message-----
From: Simone Giannecchini [mailto:simboss1@anonymised.com]
Sent: 10 August 2006 14:53
To: Adit Santokhee
Cc: geoserver-devel@lists.sourceforge.net;
geotools-devel@lists.sourceforge.net
Subject: Re: [Geotools-devel] irregular depth valuesCiao Adit,
could you please be a bit more specific? Are you talking about a
describ coverage or what?Simone.
On 8/10/06, Adit Santokhee <ads@anonymised.com> wrote:
>
> Hello all,
>
> How can we specify irregular depth values using WCS spec?
>
> E.g.(in metres) 5,30, 50, 100, 200, 400
>
> Cheers,
>
> adit
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> Geotools-devel mailing list
> Geotools-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions-------------------------------------------------------
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
How can we specify irregular depth values using WCS spec?
E.g.(in metres) 5,30, 50, 100, 200, 400
<Dimension name="elevation" units="CRS:88" unitSymbol="m" default="0">
-5, -30, -50, -100, -200, -400
</Dimension>
See Example 2, pg. 53, OGC 06-042 ; WMS 1.3.0
sorry to bother with my requests ... actually I'm going to develop a new
small project where I should filter some features from a
shapefile/database
against different attribute types which can be even time.
My take on this WMS thing is that the TIME parameter supports a start/stop
time. (e.g. including "...&TIME=2005-11-01/2005-11-30&..." in the request
should get you all of the November 2005 entries in all map layers.)
I'm probably talking way beneath your level, but I'm just now discovering
how cool this is. 
Also check out the nonspecial sample dimensions. If
server says:
<Dimension name="wavelength" units="Angstrom" unitSymbol="Ao">
3000, 4000, 5000, 6000
</Dimension>
Then you can put "...&DIM_WAVELENGTH=4000&..." in the GetMap request.
Instead of "4000", you can put a comma-separated list or an interval too
(4000/6000/1000). The key is to use "DIM_{dimensionname}". See section
C.3 in WMS1.3.0.
Now if you want to "adapt" this to a non-gridded application...heh heh...
:: To make a feature searchable by any of its attributes, there needs to be
a dimension advertised for each attribute. Say you have a "point" feature
with a temperature attribute, and you want to be able to map only those
stations with "good" readings. Your layer would advertise:
<Dimension name="temp" units="Kelvin" unitSymbol="K">0/370/0.1</Dimension>
This declares that the temperature axis is limited to 0-370 Kelvins, at an
accuracy of 0.1 K. Say any reading less than 220K (-53C) is "bad". You
make your map with "...&DIM_TEMP=220/370/0.1&...", and all the bad stations
disappear. Make it with "...&DIM_TEMP=300/370/0.1&..." and you just get
tropical stations (ish). Note that the "resolution" in min/max/resolution
is just along for the ride. Since the temperature dimension is not
gridded, you're just requesting a range. Furthermore, you can't do
anything tricky (like math.) But it should let you do basic filtering by
scalar value.
Obviously, if you wanted to search by elevation or time as well, you'd need
to declare these "Dimensions" separately. Note that you only have ONE
chance to specify a range for each dimension in the GetMap request.
Therefore, if you have one layer calibrated to Celcius and another in
Kelvins, you need to declare two dimensions (e.g. tempC and tempK) and the
server must apply the correct dimension to the correct layer. You would
then specify a celcius temperature range and a kelvin temperature range in
your request.
Your dimensions determine what you get to query by.
Mua hah hah hah.
Bryce
PS: I believe this is the answer to how we could handle "unrelated
quantities" like salinity, temperature, pressure....One dimension per
quantity.