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 <[email protected]>: > Hi Andrea, > if you need two datetime attributes for each feature (in your example, > for each county), you can use custom dimensions > http://mapserver.org/ogc/wms_dimension.html. > > Emanuele > > > On Sun, Feb 26, 2017 at 6:32 PM, Andrea Peri <[email protected]> wrote: >> 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 <[email protected]>: >>> Hi Andrea, >>> >>> The possible WMS Time parameters for MapServer are documented at: >>> http://mapserver.org/ogc/wms_time.html 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 >>> http://www.gatewaygeomatics.com/ >>> >>> >>> >>> On 2017-02-26 11:58 AM, Andrea Peri wrote: >>>> >>>> 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. >>>> >>>> >>>> http://docs.geoserver.org/latest/en/user/data/webadmin/layers.html#data-webadmin-layers-edit-dimensions >>>> >>>> So I hope it could be done also possible in mapserver. >>>> >>>> Thx. >>>> >>>> >>> >>> >>> _______________________________________________ >>> mapserver-users mailing list >>> [email protected] >>> https://lists.osgeo.org/mailman/listinfo/mapserver-users >> >> >> >> -- >> ----------------- >> Andrea Peri >> . . . . . . . . . >> qwerty àèìòù >> ----------------- >> _______________________________________________ >> mapserver-users mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/mapserver-users -- ----------------- Andrea Peri . . . . . . . . . qwerty àèìòù ----------------- _______________________________________________ mapserver-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-users
