TimeInformation request message

Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.

Time information request root element1
Version number. 0..1 1.0
Each LocalInfo element represent a location for which time and date information is requested. Requesting multiple LocalInfo is only supported for some GDS/CRS.

If only a CityCode is specified the response will return the current local time and date at the given location.

For some GDS/CRS it is also supported to specify a additional local Time and Date. In that case the response will not return the current but echo the requested local time and date and additionally return the UTC time and date corresponding to the requested local time and date.
City code for time request.

Local time in ISO 8601 format (hh:mm).

1 12:30
Local date in ISO 8601 format (yyyy-mm-dd).

1 2002-02-02


NodeName of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples:
0..3 Node is optional and may occur up to 3 times.
1..N Node must occur at least one (mandatory) and may occur any number of times.
2 Node must occur exactly twice.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server