usage of ps_range table in petascope 8.x

[damiano]

in ps_range table "uom" is ignored

[abeccati]

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.

[Piero Campalani]

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).

[Dimitar Misev]

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

[Piero Campalani]

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

[Dimitar Misev]

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

[Piero Campalani]

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 !