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

[IDV #ILT-566886]: vertical profiles with depth, not altitude

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.

  • Subject: [IDV #ILT-566886]: vertical profiles with depth, not altitude
  • Date: Wed, 14 Mar 2012 15:01:06 -0600
> > Hi Yuan,
> > Thanks for the quick reply.  The attached temperature, salinity profile
> > (from GTSPP) is very typical of the data I'm dealing with.
> > Murray
> >
> >
> 
> Murray,
> The data structure is very odd, I am not sure the ncml can work on this 
> dataset. Looking at your dataset structure:
> 
> float salinity(time=1, depth=19, latitude=1, longitude=1);
> :long_name = "Salinity";
> :short_name = "psal";
> :standard_name = "salinity";
> :units = "PSU";
> :data_min = 33.92f; // float
> :data_max = 34.15f; // float
> :C_format = "%9.4f";
> :FORTRAN_format = "F9.4";
> :_FillValue = -99.0f; // float
> :Station_Duplication_Flag = "N";
> :Digitization_Method = "7";
> :Standard = "2";
> :Deepest_Depth_m = 60.0f; // float
> :epic_code = 41; // int
> 
> 
> And the data from Alan:
> 
> float salinity(depth=78, lat=689, lon=1440);
> :_FillValue = -32000S; // short
> :missing_value = -32000.0f; // float
> :long_name = "Salinity";
> :units = "psu";
> :FORTRAN_format = "e13.6";
> :coordinate_system = "orthogonal_constant-spacing";
> :Navo_code = 16; // int
> 
> 
> Changing the direction can be done by adding:
> 
> <variable name="depth" shape="depth" type="double">
> <attribute name="positive" value="down" />
> </variable>
> 
> But this doesn't help since the IDV can not figure out the type of your data.
> 
> 
> Yuan


Murray,
    Alan's data is grid dataset, and yours is more like a profile or trajectory 
dataset. Is it right?


Yuan
> > ----- Original Message -----
> > From: "Unidata IDV Support" <address@hidden>
> > To: <address@hidden>
> > Cc: <address@hidden>; <address@hidden>
> > Sent: Tuesday, March 13, 2012 3:22 PM
> > Subject: [IDV #ILT-566886]: vertical profiles with depth, not altitude
> >
> >
> > >> Full Name: Murray Brown
> > >> Email Address: address@hidden
> > >> Organization: IOC Marine Data Mgt. Training Program
> > >> Package Version:
> > >> Operating System:
> > >> Hardware:
> > >> Description of problem: Don,
> > >> I'm not downloading NC files, so don't believe I can use the ncml
> > >> "converter" that changes positive heights to negative depths.  You
> > >> offered to show an earlier requester how to create a new DATA SOURCE TYPE
> > >> for this situation.  Could you please help me with that now.  Thanks.
> > >>
> > >> Murray Brown
> > >>
> > >>
> > > Hi Murray,
> > >      We use ncml to modify certain attributes of the dataset, there is
> > > really no difference between local or remote dataset.
> > >      I can help you create the new data type if you send me a sample file.
> > >
> > >
> > > Yuan
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: ILT-566886
> > > Department: Support IDV
> > > Priority: Normal
> > > Status: Open
> > >
> >
> >
> 


Ticket Details
===================
Ticket ID: ILT-566886
Department: Support IDV
Priority: Normal
Status: Open