I've thought about capability like this for use with Aircraft Flight Tracks as well. Since all my data is in PostGIS, I was wondering how difficult it would be to implement an analog to being able to use !BBOX! to capture the bbox part of the query and to be able to put it where you want in the SQL query and to have a !TIME! that could intercept the WMS time request and pass it through to either your query (ie where !TIME! between MIN_DATE and MAX_DATE -- wouldn't work if !TIME! was a time range) or into a custom plpgsql function.
<br><br>What I do currently is to just use %time% with mapserver cgi and variable substitution, but there isn't quite a way to port that over to WMS-T.<br><br><div><span class="gmail_quote">On 7/27/06, <b class="gmail_sendername">
Eijnden, Bart van den (AGI)</b> <<a href="mailto:b.vdeijnden@agi.rws.minvenw.nl">b.vdeijnden@agi.rws.minvenw.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Assefa,<br><br>so e.g. you would have (DD-MM-YYYY):<br><br>ROAD_SEGMENT_ID MIN_DATE MAX_DATE<br>1 01-01-2006 01-04-2006<br>2 01-03-2006 01-06-2006
<br>etc.<br><br>So these represent validity, the road segment is valid/existant between MIN_DATE and MAX_DATE.<br><br>So if I want a map with the situation of 01-05-2006, 1 would not be on it, but 2 would be.<br><br>If I would want a map with the situation of 15-03-2006 until 15-04-2006, both would be on it.
<br><br>Does this make sense?<br><br>Best regards,<br>Bart<br><br>-----Oorspronkelijk bericht-----<br>Van: UMN MapServer Users List<br>[mailto:<a href="mailto:MAPSERVER-USERS@LISTS.UMN.EDU">MAPSERVER-USERS@LISTS.UMN.EDU</a>
]Namens Yewondwossen Assefa<br>Verzonden: donderdag 27 juli 2006 3:35<br>Aan: <a href="mailto:MAPSERVER-USERS@LISTS.UMN.EDU">MAPSERVER-USERS@LISTS.UMN.EDU</a><br>Onderwerp: Re: [UMN_MAPSERVER-USERS] WMS time question<br><br>
<br>Bart,<br><br><br>Bart van den Eijnden (OSGIS) wrote:<br>> Hi list,<br>><br>> looking through the Mapserver WMS time HOWTO I wondered one thing, it is<br>> only possible to have 1 timeitem, a DB column which contains the
<br>> date/time. Ofcourse this is pretty okay for satellite images (in a<br>> tileindex) which are taken every X days/months.<br>><br>> But what happens to road network segments (geometries in Oracle Spatial<br>
> for instance) which have a minimum date and a maximum date? So you need to<br>> specify 2 timeitems (one min and one max) for that. Was this use case just<br>> not implemented?<br>><br><br> What would the min/max date represent : the valid time extents or
<br>simply 2 time fields on which we can do a query ?<br>The wms request allows to send a time value that is then compared to<br>the value inside the timeitem. Would you expect to be able to compare<br>the time request between the 2 timeitmes defined ?
<br><br>> Best regards,<br>> Bart<br>><br><br><br>--<br>----------------------------------------------------------------<br>Assefa Yewondwossen<br>Software Analyst<br><br>Email: <a href="mailto:assefa@dmsolutions.ca">
assefa@dmsolutions.ca</a><br><a href="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</a><br><br>Phone: (613) 565-5056 (ext 14)<br>Fax: (613) 565-0925<br>----------------------------------------------------------------
<br><br><br>Disclaimer<br>************************************************************************<br>Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is<br>uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
<br>hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te<br>informeren. Wij adviseren u om bij twijfel over de juistheid of de<br>volledigheid van de mail contact met afzender op te nemen.<br><br>This message shall not constitute any rights or obligations.
<br>This message is intended solely for the addressee.<br>If you have received this message in error, please delete it and<br>notify the sender immediately. When in doubt whether this message<br>is correct or complete, please contact the sender.
<br>************************************************************************<br></blockquote></div><br><br clear="all"><br>-- <br>************************************<br>David William Bitner