[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #BRP-865620]: IDV 6.2u2 Question

> I think that was it. I tried scaling the values and they appear correct.
> 
> On Thu, Apr 18, 2024 at 10:53?AM Logan Greenlee <address@hidden>
> wrote:
> 
> > Hi,
> >
> > Just a quick follow up - I just noticed that :
> >
> > double ugos(time=2, latitude=720, longitude=1440);
> >       :_FillValue = -2147483648; // int
> >       :add_offset = 0.0; // double
> >       :scale_factor = 1.0E-4; // double
> >       :missing_value = -2147483648; // int
> >       :valid_min = -48132; // int
> >       :valid_max = 49224; // int
> >       :long_name = "Absolute Geostrophic Velocity: Zonal Component";
> >       :units = "m/s";
> >       :standard_name = "surface_geostrophic_eastward_sea_water_velocity";
> >       :coordinates = "longitude latitude";
> >       :grid_mapping = "crs";
> >       :comment = "The Mean Dynamic Topography (MDT) used in the derivation
> > of the geostrophic currents is the MDT CNES/CLS 2013";
> >       :_ChunkSizes = 1U, 720U, 1440U; // uint

Hi Logan,

It appears that the attribute scale factor of the variable not defined 
correctly.
If the variable is defined as "short" or "int", then you
use the scale factor to create a double variable to restore the real values of 
the variable. In your 
case, this variable already a double, you do not add the attribute 
"scale_factor" to change 
the real values of this variable.

Yuan

> >
> > It appears that the values have a scale factor applied to them. As far as
> > I know, the scale factor is the same as all of the files come from the same
> > source. Is it possible that the scale factor is not being applied?
> >
> > address@hidden> wrote:
> >
> >>
> >> Logan Greenlee,
> >>
> >> Thank you for contacting us. This is an automated response confirming the
> >> receipt of your ticket. One of our agents will get back to you as soon as
> >> possible. For your records, the details of the ticket are listed below.
> >> When replying, please make sure that the ticket ID is kept in the subject
> >> line to ensure that your replies are tracked appropriately.
> >>
> >>     Ticket ID: BRP-865620
> >>     Subject: IDV 6.2u2 Question
> >>     Department: Support IDV
> >>     Priority: Normal
> >>     Status: Open
> >>
> >>
> >>
> >> Kind regards,
> >>
> >> Unidata User Support
> >>
> >>
> 
> 


Ticket Details
===================
Ticket ID: BRP-865620
Department: Support IDV
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with NSF Unidata User Support are recorded in the 
Unidata inquiry tracking system and then made publicly available through the 
web.  If you do not want to have your interactions made available in this way, 
you must let us know in each email you send to us.