I'm thinking land-use/land-cover changes over time. While these could
be represented by a single consensus timestamp, having a period/interval
makes more sense.
As Bart mentioned, his data are for roads and have a valid from-to timeset.
As I recall WMS time series history, the requirement was for a single
timestamp and that's what got implemented. GoMOOS, right?
gerry
Yewondwossen Assefa wrote:
Bart,
Bart van den Eijnden (OSGIS) wrote:
Hi list,
looking through the Mapserver WMS time HOWTO I wondered one thing, it is
only possible to have 1 timeitem, a DB column which contains the
date/time. Ofcourse this is pretty okay for satellite images (in a
tileindex) which are taken every X days/months.
But what happens to road network segments (geometries in Oracle Spatial
for instance) which have a minimum date and a maximum date? So you
need to
specify 2 timeitems (one min and one max) for that. Was this use case
just
not implemented?
What would the min/max date represent : the valid time extents or
simply 2 time fields on which we can do a query ?
The wms request allows to send a time value that is then compared to
the value inside the timeitem. Would you expect to be able to compare
the time request between the 2 timeitmes defined ?
Best regards,
Bart
--
Gerry Creager -- [EMAIL PROTECTED]
Texas Mesonet -- AATLT, Texas A&M University
Cell: 979.229.5301 Office: 979.458.4020 FAX 979.862.3983
MAIL: AATLT, 3139 TAMU
Physical: 1700 Research Parkway, Suite 160,
College Station, TX 77843-3139
