This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Jasmine, Yes, that is what you should do with the scale and offset. The data returned by opendap for any of the radar data variables (like reflectivity) should be single byte *unsigned* values in the range 0 to 255. Applying the scale and offset will convert them to values in the range -33 to 94.5 by the formula: scaled_value = byte_value * 0.5 + -33. If the values look weird, it's possible the opendap client you're using isn't handling the unsigned values properly and is instead giving you byte values in the range -128 to 127; in this case the negative values won't scale properly using the above formula. Ryan > Good afternoon, > Thank you for your previous answer. > > I do have another question please. > Indeed, in the reflectivity variable, it is said > - scale factor = 0.5 > - add offset = -33.0 > Are we supposed to divide each reflectivity value per 2 and add an offset > of -33dbZ per value ? > > Because, when we take a look at the reflectivity value with a scale of the > reflectivity meaning it does match so well. Ticket Details =================== Ticket ID: XRG-961762 Department: Support THREDDS Priority: Normal Status: Closed