Changes between Version 14 and Version 15 of PetascopeTimeHandling

Timestamp:

Feb 28, 2014, 7:33:29 AM (12 years ago)

Author:

Piero Campalani

Comment:

add div with subsets

PetascopeTimeHandling

@@ -53 +53 @@
 In the first place, one should be aware of the difference between the time resolution (UoM) of the T-CRS and the adopted ''offset vector'' ruling the spacing along time for the coverage: with 1-norm vectors there is no such difference, however it is perfectly possible to use either a bigger vector (e.g. equal to 7 on a day-resolution T-CRS for weekly data) or a fractional one. For more on offset vectors please refer to the ''Petascope'' [PetascopeUserGuide user guide].
 
-As with normal spatial axes, a WCS/WCPS subsets shall define numeric trimming and slicings on a CRS dimension. The [https://portal.opengeospatial.org/files/?artifact_id=50140 standard] additionally adhere to EBNF syntax [IETF 2616], allowing ''tokens'' inside double-quotes: on time dimensions then ISO:8601 datetime representations can be used in place of the usually less friendly numeric time coordinates. 
+As with normal spatial axes, a WCS/WCPS subsets shall define numeric trimming and slicings on a CRS dimension. The [https://portal.opengeospatial.org/files/?artifact_id=50140 standard] additionally adhere to EBNF syntax [IETF 2616], allowing ''tokens'' inside double-quotes: on time dimensions then ISO:8601 datetime representations can be used in place of the usually less friendly numeric time coordinates:
+
+{{{
+#!div style="background: GhostWhite; border: 5px ridge; text-align: center; width: 70%; margin-left: auto ; margin-right: auto ;" 
+{{{
+#!html
+<h3>...&service=WCS&request=GetCoverage&<u><span style="color: MediumBlue;">subset=<span style="color: DodgerBlue;">ansi</span>(150905)</span></u>&...</h3>
+<h3>...&service=WCS&request=GetCoverage&<u><span style="color: MediumBlue;">subset=<span style="color: DodgerBlue;">ansi</span>(<span style="color: MediumBlue;"><i>"2014-02-28"</i></span>)</span></u>&...</h3>
+}}}
+}}}
 
 Implementation-wise, the support for ISO datetime is extended by ''Petascope'' thanks to the [http://www.joda.org/joda-time/ Joda-Time] Java library. The datetime formatter used to convert literal to numeric time representations is the official ISO date formatter with optional time, which then permits dates only or dates plus time (plus time zone shifts). When a time zone is not defined, the library takes the default time zone of the underlying JVM, hence it was decided to force a UTC default time zone instead, to avoid platform-dependent behaviors.