> 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.
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
