usage of ps_domain table in petascope 8.x

[damiano]

in ps_domain table:

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

[abeccati]

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.

[Piero Campalani]

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.

[Piero Campalani]

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.

[Piero Campalani]

Fixed in changeset:6f4900b.