#573 closed defect (fixed)
SWE metadata from database not to be ignored
| Reported by: | Piero Campalani | Owned by: | Piero Campalani |
|---|---|---|---|
| Priority: | critical | Milestone: | 9.0 |
| Component: | petascope | Version: | development |
| Keywords: | swe metadata rangetype | Cc: | Dimitar Misev, Vlad Merticariu, Alex Dumitru, abeccati |
| Complexity: | Medium |
Description
Petascope still needs to be adjusted in order to port the SWE range-type metadata in petascopedb to the GML output.
See getAllowedValues() in petascope.wcs2.parsers.GetCoverageMetadata class.
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Partial patch in changeset:932388d, to enable allowedIntervals.
Next step is create a hierarchy of classes to reflect the SWE data model (an abstract field + a concrete quantity class are currently required).
I can personally take care of this.
comment:3 by , 10 years ago
| Cc: | added |
|---|---|
| Priority: | major → critical |
Corrige: I can personally take care of this after fixing #505. It would be important to fix this ticket before release. If somebody can handle this, please reassign it to himself/herself and accept it.
comment:4 by , 10 years ago
While patching this ticket, #476 could be fixed as well after adding NiL values support to the db schema.
comment:5 by , 10 years ago
| Status: | new → accepted |
|---|
comment:6 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Petascope updated in changeset:352f985.
Additionally, the patch also added NIL values support in the SWE field (#476).
comment:7 by , 10 years ago
While running the OGC compliance test, I realized a bug in the previous fix: swe:AllowedValues need to be enclosed in a swe:constraint element.
Petascope fixed in changeset:3d0c785.
systemtest oracles updated in changeset:b17ef6a.
Graphical petascopedb schema to include ps_nil_value in changeset:75c2cdb.
Patch submitted for enabling allowed intervals.
If doable within release, I'll follow up with a more comprehensive support of SWE so as to enable all that is available in the database (which is not all SWE metadata: see #582).
This means defining a new class for SWE metadata, whose object would be included either in the WCPS RangeElements or in the general CoverageMetadata class.