<html:div xmlns="http://www.w3.org/1999/xhtml"><p>A container feature for defining a Meteorological Object moving and evolving in time. Each timeInstance element should usually contain or refer to the same type of the feature object, unless it is the purpose to model a feature morphing from one type to another (closely related) type in time.</p><p>Allowed time interpolation methods to use when modeling the object state between the given time instances is given by allowedTimeInterpolation elements. If the element is not given, the object state is not meant to be interpolated between the given time instances.</p></html:div>
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods. This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<xs:complexType name="DynamicMeteorologicalObjectType"><xs:annotation><xs:documentation><html:div xmlns="http://www.w3.org/1999/xhtml"><p>A container feature for defining a Meteorological Object moving and evolving in time. Each timeInstance element should usually contain or refer to the same type of the feature object, unless it is the purpose to model a feature morphing from one type to another (closely related) type in time.</p><p>Allowed time interpolation methods to use when modeling the object state between the given time instances is given by allowedTimeInterpolation elements. If the element is not given, the object state is not meant to be interpolated between the given time instances.</p></html:div></xs:documentation></xs:annotation><xs:complexContent><xs:extension base="metobj:AbstractMeteorologicalObjectTimeSeriesType"><xs:sequence><xs:element name="allowedTimeInterpolation" type="metobj:timeInterpolationType" minOccurs="0" maxOccurs="unbounded"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
