Changes between Initial Version and Version 2 of Ticket #1394


Ignore:
Timestamp:
Sep 26, 2016, 11:34:19 AM (8 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1394

    • Property Component petascope → secore
    • Property Summary Petascope_Convert subset in UnixTime to seconds → SECORE_Update UnixTime to seconds

  • Ticket #1394 – Description

    initial v2  
    1 The problem is coverage which imported with UnixTime will use origin, coefficients in seconds although UoM of UnixTime is "days". Then when make a WCS GetCoverage request with correct datetime format, it convert to interval with day UoM and return error.
     1According to
     2
     3http://external.opengeospatial.org/twiki_public/TemporalDWG/TemporalCrsUris#UnixTimeDatumRdf
     4
     5UnixTime should be seconds in UoM however in SECORE it is day, so it should be updated to match the original definition with UoM in seconds.
    26
    37
    48{{{
    5 service=WCS&version=2.0.1&request=GetCoverage&coverageId=irr_cube_2_test2
    6 &subset=E(80042.7273594)&subset=N(5449865.55794)
    7 &subset=unix("2008-01-03T23:03:55Z", "2008-01-05T22:58:29Z")
    8 
    9 unix axis: subset (13881.96105324074:13883.957280092593) is out of bounds.
     9<CoordinateSystemAxis xmlns=\"http://www.opengis.net/gml/3.2\" id=\"second\" uom=\"http://www.opengis.net/def/uom/UCUM/0/s\">
     10<description>Coordinate system axis for the recording of seconds [s].</description>
     11<identifier codeSpace=\"http://www.ietf.org/rfc/rfc3986\">http://www.opengis.net/def/axis/OGC/0/seconds</identifier>
     12<remarks>Initial version (0.1)</remarks>
     13<axisAbbrev>second</axisAbbrev>
     14<axisDirection codeSpace=\"http://www.ietf.org/rfc/rfc3986\">http://www.opengis.net/def/axisDirection/OGC/1.0/future</axisDirection>
     15                </CoordinateSystemAxis>
    1016}}}
    11 
    12 This is an existing problem then need a workaround for this TimeCRS.
    13