Opened 4 years ago

Closed 3 years ago

#441 closed defect (fixed)

usage of ps_range table in petascope 8.x

Reported by: damiano Owned by: pcampalani
Priority: major Milestone: Future
Component: petascope Version: 8.5
Keywords: ps_range uom Cc: mantovani@…
Complexity: Easy

Description

in ps_range table "uom" is ignored

Change History (10)

comment:1 Changed 4 years ago by damiano

  • Summary changed from usage of table ps_range to usage of ps_range table in petascope 8.x

comment:2 Changed 4 years ago by damiano

  • Cc mantovani@… added

comment:3 Changed 4 years ago by abeccati

  • Complexity changed from Medium to Easy
  • Owner changed from abeccati to pcampalani
  • Status changed from new to assigned

Thanks for reporting Damiano, I hope this will be a quick fix for Piero otherwise we have to see if someone from the community picks-up this ticket.

Btw I assume you mean that what you put in "uom" is not part of the output of the WCS operations.

Please consider contributing a failing test case based on one of our datasets to ensure there will be no regressions on that.

comment:4 Changed 4 years ago by pcampalani

This used to work at the time I wrote the section PetascopeUserGuide#Featurespacedescription
(6 months ago): I remember I patched it already as well (changeset:5c266d).
Next week I can check this.

NOTE This case underlines a strong need for oracles in WCS tests as well (#363).

comment:5 Changed 4 years ago by dmisev

@Piero: this, #440 and #439 are outdated?

comment:6 Changed 4 years ago by pcampalani

Yes they are for rasdaman 9.0, but we might keep them open for 8.4 and 8.5 versions. ?

comment:7 Changed 4 years ago by dmisev

Do you plan to fix them for 8.5 (it's assigned to you)? Doesn't seem like some critical issue anyway.

comment:8 Changed 4 years ago by pcampalani

  • Keywords ps_range uom added
  • Milestone set to Future

comment:9 Changed 4 years ago by pcampalani

I am working on 8.5 here, and the UoM is correctly set in the response:

petascopedb=# SELECT u.uom FROM ps_coverage AS c, ps_range AS r, ps_uom AS u
petascopedb-# WHERE c.id=r.coverage AND r.uom=u.id AND c.name='mr';
 uom 
-----
 K
(1 row)

http://localhost:8080/petascope?version=2.0.0&service=WCS&request=DescribeCoverage&coverageid=mr :

...
<swe:field name="grey">
  <swe:Quantity definition="urn:ogc:def:dataType:OGC:1.1:char">
  <swe:description/>
  <swe:uom code="K"/>
...

Damiano, let me know if you can verify this !

comment:10 Changed 3 years ago by pcampalani

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