Opened 9 years ago
Closed 8 years ago
#1263 closed defect (fixed)
WCST doesn't save null values in coverage
Reported by: | Vlad Merticariu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.3 |
Component: | petascope | Version: | development |
Keywords: | Cc: | ||
Complexity: | Medium |
Description
It appears that WCST saves the coverage nil values in the rasdaman array type, but the do not appear in the coverage description, or in the tiff file, when a GetCoverage request is performed.
Change History (2)
comment:1 by , 8 years ago
Milestone: | → 9.3 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I will take this ticket as it is good for understanding wcs-t, when ingesting new coverage, it will check if there is an existing type which has the same null value from wcst_import, if not it will create a new type for this null value.
what was missed is ingesting null value to coverage metadata and when DescribeCoverage or Get Coverage, it can show these values in Range List, example:
and with GetCoverage in WCS (i.e: tiff file) it should keep the setted nodata value in the tiff tag
for example