Opened 16 years ago
Closed 14 years ago
#2241 closed defect (fixed)
GRIB/JPEG2000 Scaling Differences
Reported by: | warmerdam | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | unspecified |
Severity: | normal | Keywords: | grib jp2kak jp2ecw jasper |
Cc: | retsios, sherman@…, Mateusz Łoskot |
Description (last modified by )
Examining channel 7 of gfs06zf03.grib2 we see the scaling of the values differs significantly depending on whether they are read with JP2KAK or JP2ECW.
JP2KAK
Band 7 Block=360x1 Type=Float64, ColorInterp=Undefined Description = 2000[Pa] ISBL="Isobaric surface" Computed Min/Max=24099.689,24279.850
JP2ECW
Band 7 Block=360x1 Type=Float64, ColorInterp=Undefined Description = 2000[Pa] ISBL="Isobaric surface" Computed Min/Max=24099.689,26901.289
I think this is more an issue with how the different jpeg2000 drivers handle non-integer datasets than it is about the grib driver itself.
JasPer looks like:
Band 7 Block=360x1 Type=Float64, ColorInterp=Undefined Description = 2000[Pa] ISBL="Isobaric surface" Computed Min/Max=24099.689,26901.289
Based on this, and visual examination, I am now supposing this is a problem with the JP2KAK driver. I will extract the jpeg2000 data stream for this band and dig into it deeper.
Change History (3)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|---|
Keywords: | jp2ecw removed |
Status: | new → assigned |
comment:2 by , 16 years ago
Cc: | added; removed |
---|---|
Keywords: | jp2ecw jasper added |
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I see that the JP2KAK driver now produces the same values as the other drivers so apparently the issue was solved in either Kakadu itself or the JP2KAK driver in the meantime.