[WMS] support of the Nearest Value for time dimension

[assefa]

e-mail conversations on this subject :
 
If a WMS has a time extent of:
 2001-10-30/2004-10-30
 ..of, let's say, daily observations, and my time request is:
 2000-10-30/2002-10-30
 ...is this extent out of range?


response from wms-dev :

If the available dates are declared as 2001-10-30/2004-10-30/P1D and the 
request is for 2000-10-30/2002-10-30/P1D, then I recommend the following:

(a) IF attribute 'nearestValue' is missing or has the value 0, then issue an 
InvalidDimensionValue exception.

(b) ELSE return content for 2001-10-30/2002-10-30/P1D and include the HTTP 
response header "Warning: 99 Nearest value used: TIME=2001-10-30/2002-10-
30/P1D".

See WMS 1.1.1 Annexes C.3 & C.5.2 or WMS 1.3/ISO DIS 19128 Annexes C.2 & C.4.3.
(Note error in WMS 1.1.1, p.59 where the plural "nearestValues" is used in the 
text.)

-Jeff DLB, Editor


Currently the Nearest Value is not used.

[assefa]

Won't be adressed for thsi release.