Opened 6 years ago

Closed 6 years ago

#2038 closed defect (fixed)

petascope_wrong domain extent for regular time axis

Reported by: Bang Pham Huu Owned by: Bang Pham Huu
Priority: major Milestone: 9.8
Component: petascope Version: 9.7
Keywords: Cc: Dimitar Misev, Vlad Merticariu
Complexity: Medium

Description

Import with this configuration in ingredient file for time axis (time values fetched from file names):

"timeeeeeeeeeeeeeee": {
    "min": "datetime(regex_extract('${file:name}', '(.*)\\.(.*)',1), 'YYYYMMDD')",
    "crsOrder": 0,
    "gridOrder": 0,
    "type": "ansidate",
    "resolution": 7,
    "dataBound": false
},

and input files:

            "20031228.nc",
            "20031229.nc",
            "20031230.nc"

Then, DescribeCoverage's result with time axis's extent is:

"2003-12-21T00:00:00.000Z" to "2003-12-28T00:00:00.000Z"

While it should be this extent as these input files belong to the same 7 days resolution

"2003-12-23T00:00:00.000Z" to "2003-12-30T00:00:00.000Z"

Change History (4)

comment:1 by Vlad Merticariu, 6 years ago

You are missing the timestep parameter from the ingredient, that one specifies what the 7 means (hours, days, seconds).

in reply to:  1 comment:2 by Bang Pham Huu, 6 years ago

Replying to vmerticariu:

You are missing the timestep parameter from the ingredient, that one specifies what the 7 means (hours, days, seconds).

There is nothing called "timestep" in wcst_import folder as I searched. Also, I didn't know about this parameter you mentioned.

comment:3 by Vlad Merticariu, 6 years ago

It's avaialble in the time series regular recipe, not sure about general coverage: http://doc.rasdaman.org/05_geo-services-guide.html#regular-timeseries

comment:4 by Bang Pham Huu, 6 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.