Changes between Version 20 and Version 21 of PetascopeTimeHandling

Timestamp:

Dec 7, 2017, 9:54:23 AM (6 years ago)

Author:

Peter Baumann

Comment:

—

PetascopeTimeHandling

@@ -112 +112 @@
 In addition to the inclusion of time in the compound CRS where a coverage is located, importing irregular time series in [PetascopeUserGuide Petascope] is also possible, although this not connected to the definition of perhaps a different T-CRS. The topology of a coverage (along the time dimension in this case) is independent of the way time is measured.
 
-To import irregular time series you can either manually insert in `petascopedb` the so-called vector weighting '''coefficients''' of the offset vector along time (see the ''Petascope'' [PetascopeDevGuide dev-guide]) or otherwise use our ''rasgeo'' component to handle the irregular time series directly with absolute time coordinates via the `'--z-coords'` parameter of `rasimport` (see [RasgeoUserGuide user guide] for more details).
+To import irregular time series you can either manually insert in `petascopedb` the so-called vector weighting '''coefficients''' of the offset vector along time (see the ''Petascope'' [PetascopeDevGuide dev-guide]) or use the mechanism provided by `GeneralGridCoverage` in OGC CIS 1.1.
 
 To better understand the meaining of (GML) weighting vector [http://schemas.opengis.net/gml/3.3/referenceableGrid.xsd coefficients], the general principle to decode numeric time coordinates is that the time coordinate `T'` is the representation of `(c_T' * v_t)` time steps (T-CRS UoM) from the epoch of the T-CRS, being `v_t` the scalar norm of the offset vector of the coverage along time and `c_T'` the coefficient associated to T'.