<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Helvetica, Arial, sans-serif">Hi all,</font></p>
<p><font face="Helvetica, Arial, sans-serif">Related to this discussion, there's the
</font>OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data:
<a class="moz-txt-link-freetext" href="http://www.opengis.net/doc/bp/wms-tnz/1.0">
http://www.opengis.net/doc/bp/wms-tnz/1.0</a></p>
<p>Regards -- Alex<br>
</p>
<pre class="moz-signature" cols="72">Alexandre Leroux, M.Sc., ing.
Senior geospatial specialist /
Spécialiste principal en géomatique
Data, Performance and Standards Section /
Section des Données, performance et standards
Meteorological Service of Canada /
Service météorologique du Canada
Environment and Climate Change Canada /
Environnement et Changement climatique Canada
<a class="moz-txt-link-abbreviated" href="mailto:alexandre.leroux@canada.ca">alexandre.leroux@canada.ca</a> - (514) 421-5024</pre>
<div class="moz-cite-prefix">On 02/27/2017 02:26 AM, Andrea Peri wrote:<br>
</div>
<blockquote cite="mid:CABqTJk9S-8u8-nwCOjy+URJyndaqwoWDy0L88ij6D41-=HzAFA@mail.gmail.com" type="cite">
<pre wrap="">I see it.
You have right infact I could define something like:
wms_dimensionlist: = start_date, end_date
wms_start_date_item= time
wms_end_date_item= time
wms_start_date_extent= "1900/01/01"
wms_end_date_extent= "2999/01/01"
wms_start_date_default=current
wms_end_date_default=current
This could be a solution on wms server side, but on client side it
need to have a wms client able to understant wms-dimension.
Actually my client interface is able to recognize and use a wms-time
but not able to recognize and use correctly a wms-dimensional from
getcapabilities.
:(
A.
2017-02-27 7:48 GMT+01:00 Emanuele Di Giacomo <a class="moz-txt-link-rfc2396E" href="mailto:edigiacomo@arpae.it"><edigiacomo@arpae.it></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Andrea,
if you need two datetime attributes for each feature (in your example,
for each county), you can use custom dimensions
<a class="moz-txt-link-freetext" href="http://mapserver.org/ogc/wms_dimension.html">http://mapserver.org/ogc/wms_dimension.html</a>.
Emanuele
On Sun, Feb 26, 2017 at 6:32 PM, Andrea Peri <a class="moz-txt-link-rfc2396E" href="mailto:aperi2007@gmail.com"><aperi2007@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Jeff.
I was understanding the wms_timeextend as defined in the annex C3 of OGC.
AFAIK it is the domains of availability for the values in the
time-field in all the dataset
But is always one only attribute. This is ok for spot events. Instead
when there is a dataset where every feature is a start-date and an
end-date of validity for every single feature of dataset.
As example:
the dataset of county boundaries. Sometime the county bounaries could
change so they have a startdate and an enddate.
So is need to define both: the end-date and the start-date using two
attribute fields.
I wrong to understand the wms_timeextend ?
Thx,
A.
2017-02-26 17:29 GMT+01:00 Jeff McKenna <a class="moz-txt-link-rfc2396E" href="mailto:jmckenna@gatewaygeomatics.com"><jmckenna@gatewaygeomatics.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Andrea,
The possible WMS Time parameters for MapServer are documented at:
<a class="moz-txt-link-freetext" href="http://mapserver.org/ogc/wms_time.html">http://mapserver.org/ogc/wms_time.html</a> There is a "wms_timeextent"
parameter that sets the possible start/end time range, but I am not sure if
I am understanding your question fully.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
<a class="moz-txt-link-freetext" href="http://www.gatewaygeomatics.com/">http://www.gatewaygeomatics.com/</a>
On 2017-02-26 11:58 AM, Andrea Peri wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Hi,
I need to define a WMS Time for using on an our dataset.
But I need colud define also a End-Time attribute. Because a single
feature has a
start-time validity and an end-time validity.
Searching for some workaround on internet, I see that this option
(start-time and end-time of validity for a feature) is allowed in
geoserver.
<a class="moz-txt-link-freetext" href="http://docs.geoserver.org/latest/en/user/data/webadmin/layers.html#data-webadmin-layers-edit-dimensions">http://docs.geoserver.org/latest/en/user/data/webadmin/layers.html#data-webadmin-layers-edit-dimensions</a>
So I hope it could be done also possible in mapserver.
Thx.
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
mapserver-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/mapserver-users">https://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
</pre>
</blockquote>
<pre wrap="">
--
-----------------
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-----------------
_______________________________________________
mapserver-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/mapserver-users">https://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>