I've tried to be a bit more specific in this new page for the docs (note
it's not committed yet and doesn't describe current behavior, but what I'm
currently thinking should be implemented.)
https://github.com/dwins/geoserver/blob/feature-reduced-accuracy-time/doc/en/user/source/services/wms/time.rst
No unit tests (published) yet but here's what I'm currently thinking.
By the way, I noticed that section C.3.2 has this line (emphasis added):
> In either case, value uses the format described in Table C.2 to provide a
> single value, a comma-separated list, *or
> an interval of the form start/end without a resolution*.
So it turns out that's not a GeoServer-specific extension after all :)
--
David Winslow
OpenGeo - http://opengeo.org/
On Wed, Aug 15, 2012 at 11:55 AM, Martin Davis <[email protected]> wrote:
>
>
> On Wed, Aug 15, 2012 at 6:41 AM, Andrea Aime <[email protected]
> > wrote:
>
>> On Wed, Aug 15, 2012 at 12:53 AM, Martin Davis <[email protected]>wrote:
>>
>>> And we also don't know the underlying precision in the data, right? So
>>> this would effectively say that every request time value requires full
>>> precision.
>>>
>>> It's hard to see clients relying on exceptions being thrown if they fail
>>> to heed the absence of declared nearest-value behaviour. Pretty complex
>>> semantics for that. So maybe this doesn't stop a server from being more
>>> lenient in what it accepts.
>>>
>>
>> Or maybe not? I'm _not sure_ if I'm getting out of topic or not, but I've
>> definitely seen the CITE tests checking for the
>> server throwin service exceptions back when some things are not up to
>> expectations with time and dimension.
>> Have a look at the CITE tests assertions here:
>>
>> https://svn.opengeospatial.org/ogc-projects/cite/scripts/wms/1.3.0/tags/r3/ctl/dimensions.xml
>>
>
> Good idea to check that. I see the following two tests in that CITE doc
> which check for MissingDimensionException:
>
> * When a layer that has a dimension without a default value is requested
> without supplying the dimension parameter, the response is an exception
> with code=MissingDimensionValue.
> * If the dimension decalaration does not include a default value, a
> request without a TIME parameter produces an exception with
> code=MissingDimensionValue.
>
> Neither of these sound like they're testing the nearest-value behaviour.
> So I guess it's still be bit of spec tea-leaf reading.
>
>
>>
>> Cheers
>> Andrea
>>
>>
>> --
>> ==
>> Our support, Your Success! Visit http://opensdi.geo-solutions.it for
>> more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via Poggio alle Viti 1187
>> 55054 Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax: +39 0584 962313
>> mob: +39 339 8844549
>>
>> http://www.geo-solutions.it
>> http://twitter.com/geosolutions_it
>>
>> -------------------------------------------------------
>>
>>
>
>
> --
> Martin Davis
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
