| Created: | 8/01/2015 1:28:31 PM |
| Modified: | 13/05/2015 9:34:24 PM |
 Project: |
|
| Advanced: |
|
The Time Value Pair (TVP) Encoding schema contains types suitable for encoding TimeSeries (both Measurement and Categorical) in a sequence of time, value pairs.<br /></p><p>Note that this time, value pair encoding of timeseries encoding takes the name 'TimeseriesTVP'. The domain range encoding equivalent takes the name TimeseriesDomainRange. <br /></p>
- Tagged Values
- Constraints
- Scenarios
- Other Links
| Tag | Value |
| xsdDocument | timeseriesTVP.xsd |
 Details:
Description: Valid file name or relative file name of the XSD file to create for representing the contents of the package
|
|
| Constraint | Type | Status |
| http://www.opengis.net/spec/timeseries/1.0/req/uml-timeseries-core | Invariant | Approved |
|
Details:
|
||
| http://www.opengis.net/spec/timeseries/1.0/req/uml-timeseries-tvp | Invariant | Approved |
|
Details:
|
||
| http://www.opengis.net/spec/timeseries/1.0/req/uml-categorical-timeseries-tvp | Invariant | Approved |
|
Details:
|
||
| http://www.opengis.net/spec/timeseries/1.0/req/uml-measurement-timeseries-tvp | Invariant | Approved |
|
Details:
|
||
| http://www.opengis.net/spec/timeseriesml/1.0/req/xsd-xml-rules | Invariant | Approved |
|
Details:
|
||
| Scenario | Type |
| /req/xsd-timeseries-tvp/valid | Basic Path |
|
Details:
The content model of this XML element shall have a value that matches the content model defined by tsml:TimeseriesTVP.
Steps:
1. Verify that the XML instance is a valid timeseries.
|
|
| /req/xsd-timeseries-tvp/time-increasing | Alternate |
|
Details:
The domain elements (implemented as the tsml:point element) shall be ordered in increasing time.
Steps:
1. Verify that each point in the timeseries is increasing in time.
|
|
| /req/xsd-timeseries-tvp/record-homogenous | Alternate |
|
Details:
The type of the tsml:value element (range) shall be the same for each point in the timeseries, with the exception null values which may be used on any value.
Steps:
1. Verify that the record type for each point in the series is the same. E.g. all of type MeasurementTVP or CategoricalTVP.
|
|
| /req/xsd-timeseries-tvp/domain-time | Alternate |
|
Details:
The domain of the timeseries coverage shall consist only of a temporal component.
Steps:
1. Verify that the XML instance is a valid coverage timeseries consisting of single temporal element.
|
|
| /req/xsd-timeseries-tvp/default-point-metadata | Alternate |
|
Details:
If the element defaultPointMetadata is present, the specified metadata elements apply as default values to all subsequent point elements encoded in the timeseries. If a metadata element is specified for a point then it overrides the default value. For elements with multiple cardinality (e.g. qualifiers), defaults shall be overridden if a single element is defined in the metadata.
Steps:
1. Ensure the default metadata is applied to each point in the timeseries unless it has been overridden.
|
|
| /req/xsd-timeseries-tvp/equidistant-encoding | Alternate |
|
Details:
If the <i>baseTime </i>and <i>spacing </i>elements are defined, the <i>time </i>element shall not be encoded. The time instants shall be calculated according to the follow:<br /></p><p>time (n) = baseTime + (n * spacing) <br /></p><p>n = zero-based point index. <br /></p><p><br /></p><p>e.g. baseTime= 2011-01-01T00:00:00, spacing=P15M<br /></p><p>points: <br /></p><p>[0] - 2011-01-01T00:00:00<br /></p><p>[1] - 2011-01-01T00:15:00<br /></p><p>[2] - 2011-01-01T00:30:00<br /></p><p>[3] - 2011-01-01T00:45:00<br /></p><p>[4] - 2011-01-01T01:00:00<br /></p>
Steps:
1. Ensure the equidistant timeseries metadata has been sufficiently defined.
|
|
| /req/xsd-timeseries-tvp/time-mandatory | Alternate |
|
Details:
If the baseTime and spacing elements are not present, the time element shall be encoded.
Steps:
1. Ensure that the time component of the timeseries coverage is sufficiently specified.Ensure each point in the series has a time specified, either through definition of an equidistant series or explicitly for each point.
|
|
| /req/xsd-timeseries-tvp/null-value | Alternate |
|
Details:
To indicate a value is null, the xsi:nil attribute shall be set to ‘true’.
Steps:
1. Ensure that @xsi:nil = 'true' is specified for each point that is defined as null.
|
|
| /req/xsd-timeseries-tvp/null-point-reason | Alternate |
|
Details:
If a point is specified as null, a nilReason or censoredReason shall be provided.
Steps:
1. Ensure that a reason is specified for each point that is defined as null.
|
|
| /rec/xsd-timeseries-tvp/nil-reason-vocab | Alternate |
|
Details:
When specifying a null point reason (nilReason), one of the following URLs should be used: <br /></p><p><ul><li>Inapplicable (http://www.opengis.net/def/nil/OGC/0/inapplicable) </li><br /></p><p><li>Missing (http://www.opengis.net/def/nil/OGC/0/missing) </li><br /></p><p><li>Template (http://www.opengis.net/def/nil/OGC/0/template) - value will be available at later date. </li><br /></p><p><li>Unknown (http://www.opengis.net/def/nil/OGC/0/unknown) </li><br /></p><p><li>Withheld (http://www.opengis.net/def/nil/OGC/0/withheld.html) </li><br /></p><p></ul><br /></p>
|
|
| Object | Type | Connection | Direction | Notes |
| «ApplicationSchema» TimeseriesML GML Application Schema | Package | Package | From |