[mapserver-users] wcs_timeposition: explicit listing orstart/endrange?

[Steve Lime]

The WCS 1.1 implementation might be more flexible than the 1.0 one. Frank would be able
to comment further I suspect.

Steve

>>> On 8/15/2008 at 12:07 PM, in message
<e32c6ce00808151007t14a10381sc05c9330772ae222 at mail.gmail.com>, "Alexander
Petkov" <greenkov at gmail.com> wrote:
> OK, I will see how I can do that.
> 
> A brief glance at the code shows intent to figure out time positions
> from the wcs_timeitem parameter if  wcs_timeposition is being set to
> "AUTO"
> 
> Alex
> 
> On Fri, Aug 15, 2008 at 10:59 AM, Steve Lime <Steve.Lime at dnr.state.mn.us> 
> wrote:
>> Hi Alex: A present no,  you have to be explicit. If you file a bug I'll make 
> sure this
>> gets synced with the WMS implementation.
>>
>> Steve
>>
>>>>> On 8/15/2008 at 10:49 AM, in message
>> <e32c6ce00808150849o3163ca04j89a8f5db801eee73 at mail.gmail.com>, "Alexander
>> Petkov" <greenkov at gmail.com> wrote:
>>> I am trying to allow data downloads via a GetCoverage requests from a
>>> mapserver-backed web coverage service.
>>>
>>>>From the documentation, it would appear that the  wcs_timeposition in
>>> a layers'  metadata section can specify the start and end time
>>> positions for the layer.
>>> wcs_timeposition
>>>
>>>     * Description: (Optional) A list of the start and end time of a
>>> given coverage (i.e. "2000-11-11T11:11:11Z,2001-11-11T11:11:11Z"),
>>> used when advertising GetCapabilities.
>>>
>>> However, in practice, it looks like each time position needs to be
>>> listed explicitly, or else an exception is thrown:
>>> <ServiceExceptionReport version="1.2.0"
>>> xsi:schemaLocation="http://www.opengis.net/ogc
>>> http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd">
>>> <ServiceException code="InvalidParameterValue" locator="time">
>>> msWCSGetCoverage(): WCS server error. The coverage does not have a
>>> time position of 2005-12-20.
>>>
>>> </ServiceException>
>>> </ServiceExceptionReport>
>>>
>>> Is it possible to define the time extent with start and end time
>>> stamps, and time resolution, similar to the wms_timeextent parameter?
>>> Otherwise, my time position list would end up being rather long for a
>>> coverage that has data for several years...
>>>
>>> TIA,
>>> Alex
>>> _______________________________________________
>>> mapserver-users mailing list
>>> mapserver-users at lists.osgeo.org 
>>> http://lists.osgeo.org/mailman/listinfo/mapserver-users 
>>
>>
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org 
> http://lists.osgeo.org/mailman/listinfo/mapserver-users