Opened 10 years ago
Closed 9 years ago
#5365 closed defect (fixed)
0 min, max values
Reported by: | hmzhu | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | 1.10.1 |
Severity: | normal | Keywords: | |
Cc: |
Description
Well, this is an old issue found one year ago. In GDAL1.10.1, the value of each pixel is held successfully after source RST file is opened with UPDATE mode. This fixes the error of 0 for all values. But in the metadata file with RDC extension, both of the two become 0. Since Display min and Display max are set to equal to min and max values by default. So they are also 0 now.
Admittedly RST file with 0 min and max values in their metadata file still can be opened in other software without any problem, such as ArcGIS. But the way Idrisi display images depends on values in metadata, which raises such issues.
Solution: Fill default min and max values (which are 0s) with new values by computing them. This practice also can eliminate the risk of incorrect min and max values caused by potential change of pixel values when the open mode is UPDATE.
This is done in revised Idrisi trunk version.
Attachments (2)
Change History (5)
by , 10 years ago
Attachment: | slopes_original.jpg added |
---|
by , 10 years ago
Attachment: | slopes_after_conversion.jpg added |
---|
This is same image but after used as source data with UPDATE
comment:1 by , 10 years ago
I'm not sure to understand what you want : backport changes from trunk into 1.10 branch ? Or is there still an issue with trunk ?
Does it relate with http://trac.osgeo.org/gdal/changeset/26033/trunk/gdal/frmts/idrisi / #4980 ?
comment:2 by , 10 years ago
Any link with #5126 ? Please avoid creating duplicated tickets. It is very confusing.
comment:3 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Closing due to lack of feedback.
This is the original image before opening with UPDATE