-
Notifications
You must be signed in to change notification settings - Fork 15
Expand file tree
/
Copy pathModelTimeSeries.html
More file actions
43 lines (40 loc) · 2.01 KB
/
Copy pathModelTimeSeries.html
File metadata and controls
43 lines (40 loc) · 2.01 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
<h3>Time series</h3>
<p>
Many executions are made as parts of a time series.
There are a number of ways these may be modeled using the SSN Ontology.
</p>
<p>
The most explicit representation has each member of the series as an individual member of a <a
href="#Collections">Collection</a>.
For example <a href="#Fig-timeseries-oc"></a> shows a <a href="#SOSAObservationCollection">Collection of
Observations</a> that has a member for each time-step in the series.
</p>
<figure id="Fig-timeseries-oc">
<embed alt="Explicit time-series" src="./images/timeseries-oc.svg" style="width:100%" />
<figcaption>
Collection of observations of the same property on the same feature of interest, with each member representing a
step in the time-series.
<br>
<em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
</figcaption>
</figure>
<pre class="example turtle" data-include="./rdf/examples/timeseries-oc.ttl" data-include-format="text"></pre>
<p>
Alternatively, the series may be represented as a single <a href="#SOSAObservation">Observation</a> whose result is
a complex value, such as a vector or array.
This may be indicated 'inline' as a complex literal, e.g. CSV:
</p>
<pre class="example turtle" data-include="./rdf/examples/timeseries-result-inline.ttl" data-include-format="text"></pre>
<p>
In this example, an OGC SWE Common `DataRecord` ([[SWE-Common]], [[SWE-Common-JSON]]) is used to
define an RDF Datatype that encodes data records encoded in CSV.
</p>
<p>
The result of a time series observation can also be 'linked' to an external resource:
</p>
<pre class="example turtle" data-include="./rdf/examples/timeseries-result-link.ttl" data-include-format="text"></pre>
<p>
In addition to the encodings shown above, terms from SOSA can be directly integrated into existing structures, such
as OGC Coverages [[CoverageJSON]].
In such cases, it is no longer necessary to provide a paired Observation.
</p>