Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hi, ToolsUI ncdump returns negative values for unsigned byte attribute values from the following OPeNDAP resource: ----------------------------------------------- netcdf dods://eosdap.hdfgroup.uiuc.edu:8080/opendap/data/NASAFILES/hdf4/MOD10_L2.A2000065.0040.005.2008235221207.hdf { dimensions: Along_swath_lines_500m = 4060; Cross_swath_pixels_500m = 2708; variables: byte Snow_Cover(Along_swath_lines_500m=4060, Cross_swath_pixels_500m=2708); :_Unsigned = "true"; :coordinates = "Latitude Longitude"; :long_name = "Snow covered land"; :units = "none"; :format = "I3"; :coordsys = "cartesian"; :valid_range = 0B, -2B; // byte :_FillValue = -1B; // byte ---------------------------------------------------------------------------------------------- Should this be regarded OK because java-netcdf explicitly set _Unsigned = "true"? Or is it the problem of netcdf-java client (like IDV/Panoply) if the client cannot visualize this data properly? Here, I assume that java-client misinterpreted valid_range attribute values [0B, -2B] as they are without checking the _Unsigned = "true". Or should the hdf4_handler add a special attribute _Unsigned=true? If so, will netcdf-java return correct valid_range = 0B, 254B? Thanks, -- Are your big (Earth) data in HDF(-EOS)?
netcdf-java
archives: