This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English version of the page.

Note: This page has been translated by MathWorks. Click here to see
To view all translated materials including this page, select Country from the country navigator on the bottom of this page.

Time property

Requested time extent


The WMSMapRequest.Time property stores time as a character vector or a double indicating the desired time extent of the requested map. When you set the property, 'time' must be the value of the Layer.Details.Dimension.Name field. The default value is ''.

Time is stored in the ISO® 8601:1988(E) extended format. In general, the Time property is stored in a yyyy-mm-dd format or a yyyy-mm-ddThh:mm:ssZ format, if the precision requires hours, minutes, or seconds. You can use several different character vector and numeric formats to set the Time property, according to the following table (where dateform number is the number used by the Standard MATLAB® Date Format Definitions). Express all hours, minutes, and seconds in Coordinated Universal Time (UTC).

Dateform (number)Input (character vector)Stored format
0dd-mm-yyyy HH:MM:SSyyyy-mm-ddTHH:MM:SSZ
6mm/ddyyyy-mm-dd (current year)
14HH:MM:SS PMyyyy-mm-ddTHH:MM:SSZ
16HH:MM PMyyyy-mm-ddTHH:MM:00Z
21mmm.dd,yyyy HH:MM:SSyyyy-mm-ddTHH:MM:SSZ
23mm/dd/yyyy yyyy-mm-dd
29yyyy-mm-dd yyyy-mm-dd
31yyyy-mm-dd HH:MM:SSyyyy-mm-ddTHH:MM:SSZ

Inputs using the dateform numbers 13–16 return the date set to the current year, month, and day. Use of other dateform formats, especially 19, 20, 24, and 25, results in erroneous output.

In addition to these standard MATLAB dateform formats, the WMSMapRequest.Time property also accepts the following inputs.

Input (character vector)Description
'current'The current time holdings of the server
numeric datenumNumeric date value converted to yyyy-mm-dd (dateform 29 format)
ByyyyB.C.E. year

Use the prefixes K, M, and G, followed by a character vector number (thousand, million, and billion years, respectively), for geologic data sets that refer to the distant past.