Opened 4 years ago

Closed 4 years ago

#332 closed defect (wontfix)

Support for time in GML coverage output

Reported by: dmisev Owned by: abeccati
Priority: major Milestone: 9.0
Component: petascope Version: 8.4
Keywords: Cc: pbauman, pcampalani, abeccati
Complexity: Medium

Description

Only integer/floats are supported by GML, so having a time axis can not be encoded in the coverage output, or it can be encoded by breaking the XML schema validation.

Change History (5)

comment:1 Changed 4 years ago by pcampalani

I am afraid this will not be possible Dimitar, as I got it from some discussion in the OGC mailing lists.
Temporal coordinates will need to be printed as they are (numbers): the application, knowing the temporal CRS, will be able to convert them to dates/timestamps.

What we can/will do is allow dates/timestamps in the W*S requests.

?

comment:2 Changed 4 years ago by dmisev

Yes so one idea is to break the schema anyway for users who are fine with that.

We could introduce a flag in petascope.properties to enable/disable this.

comment:3 Changed 4 years ago by dmisev

I'm not sure, how can we proceed with this? Closing as wontfix?

comment:4 Changed 4 years ago by pcampalani

I think so, we would lose OGC compliance.
Time can be handled in input queries, both WCS and WCPS, but we keep numeric coords in the GML.

$ grep "t \?(\"" ~/rasdaman/systemtest/testcases_services/test_wcps/queries/ ~/rasdaman/systemtest/testcases_services/test_wcs/queries/ -Rh
    t("1950-01-02"),
subset=t("1950-01-01")
subset=t("1950-01-01","1950-01-05")
subset=t("1950-01-07T12:00")

comment:5 Changed 4 years ago by dmisev

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.