Opened 4 years ago

Closed 3 years ago

#440 closed defect (fixed)

usage of ps_domain table in petascope 8.x

Reported by: damiano Owned by: pcampalani
Priority: major Milestone: Future
Component: petascope Version: 8.5
Keywords: strlo strhi uom ps_domain Cc: mantovani@…
Complexity: Medium

Description (last modified by damiano)

in ps_domain table:

  • "strlo" and "strhi", if filled, cause errors in DescribeCoverage? requests,
  • "uom" is ignored

Change History (8)

comment:1 Changed 4 years ago by damiano

  • Description modified (diff)
  • Summary changed from usage of ps_range table in petascope 8.x to usage of ps_domain table in petascope 8.x

comment:2 Changed 4 years ago by damiano

  • Cc mantovani@… added

comment:3 Changed 4 years ago by abeccati

  • Owner changed from abeccati to pcampalani
  • Status changed from new to assigned

Thanks for reporting Damiano,
I think this is expected in this version since only numeric values are supported by the domain. I'll forward that to Piero for further investigation.

Is the uom issue related to #441 ? In that case I think we need to have only one place where uom is specified, the other should be removed or marked as rightfully not used.

comment:4 Changed 4 years ago by pcampalani

I can see that Petascope does read the uom associated to a domain element, but then they are not inserted in the GML: actually there is no room there for domain UoMs?, only for @srsName and @srsDimension, I believe. So we could actually drop the ps_domain.uom column.

comment:5 Changed 4 years ago by pcampalani

regarding srtLo' and 'strHi', I am reporting from the schema update script (./applications/petascope/src/main/db/petascope/update0.sql`):

-- If the type is not temporal, numLo and numHi must be the lowest and highest addressable points in geo coordinates, and strLo and strHi must be left null.
-- If the type is temporal, numLo and numHi must be left null, and strLo and strHi must be timestamps, specifying the extent.
-- Because the current implementation does not currently support temporal axes, you can use "other" as the type and specify dummy values for numLo and numHi.

comment:6 Changed 4 years ago by pcampalani

  • Keywords strlo strhi uom ps_domain added
  • Milestone set to Future

comment:7 Changed 4 years ago by pcampalani

Fixed in changeset:6f4900b.

comment:8 Changed 3 years ago by pcampalani

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