Opened 17 years ago
Closed 17 years ago
#2167 closed defect (fixed)
PROCESSING LUT= always shows highest value as white (mapdrawgdal.c)
| Reported by: | hulst | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | GDAL Support | Version: | 5.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Hi,
I have been trying the PROCESSING LUT_n="" directives. They work, but I found that the highest value in the raster is always colored white. That is, in my opinion, not desirable because I would be able to set my own out value there. Please refer to the attachments hs_saturated.png (white spot) and hs.png (white spot removed). The latter image was created using shp2img on the raster.map and hs.tif files after I modified mapdrawgdal.c, line 997 of revision 6358 so that it only appends a value pair 255:255 when the user did not specify a 255:x pair (see attachment). Note that I've modified my first idea stated on the mailinglist that a pair should not be appended when the user puts any value in the PROCESSING directive.
Best regards, Sander
Attachments (6)
Change History (9)
by , 17 years ago
| Attachment: | hs_saturated.png added |
|---|
by , 17 years ago
by , 17 years ago
by , 17 years ago
by , 17 years ago
| Attachment: | raster.map added |
|---|
comment:1 by , 17 years ago
by , 17 years ago
| Attachment: | mapdrawgdal.c added |
|---|
comment:2 by , 17 years ago
| Version: | 4.10 → 5.0 |
|---|
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Sander,
I have applied this simplified patch in trunk as r6395. It looks like an excellent adjustment!
Best regards,
hs.2.png should be ignored