Error on WC*S query with binary encoding and ISO temporal subsets

[Piero Campalani]

When setting the parameters for GDAL (RasQL encode), temporal subsets are not translated to numeric coordinates.
Temporal subsets can be either numerical or ISO timestamps
(see PetascopeTimeHandling).

Usually time is sliced out in a time-series coverage, so parameters for GDAL are generally spatial coordinates.

Encoding of spatio-temporal 2D sections should be properly allowed anyway.

A related ticket is #708: GDAL will put an empty CRS in case we set a spatio-temporal compounding.

Test queries:

http://localhost:8080/rasdaman/ows/wcs2
    ?service=WCS
    &version=2.0.1
    &request=GetCoverage
    &coverageid=eobstest
    &subset=t("1950-01-01","1950-01-05")
    &subset=Long(50)
    &format=image/tiff

for c in (eobstest)
return encode(
  (c[t("1950-01-01":"1950-01-05")])
  [Long(30:35), Lat(0)]
, "png")

For some reference code, refer e.g. to convertToInternalGridIndices() method in petascope.util.CrsUtil:

$ grep "public static.*{" ~/rasdaman/applications/petascope/src/main/java/petascope/util/TimeUtil.java 
    public static boolean isValidTimestamp (String timestamp) {
    public static boolean isOrderedTimeSubset (String timestampLo, String timestampHi) throws PetascopeException {
    public static String minusEpsilon(String timestamp) {
    public static String plus(String timestamp, Double coefficient, String timeResolution) throws PetascopeException {
    public static String coordinate2timestamp(Double numCoordinate, String datumOrigin, String timeResolution) throws PetascopeException {

[Bang Pham Huu]

This ticket actually the same as in
​http://rasdaman.org/ticket/1005 (which I'm doing) then I will close it here.