[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Support #UPW-774161]: RE: [idvusers] Access to the Unidata and NSF xml catalogs in IDV
- Subject: [Support #UPW-774161]: RE: [idvusers] Access to the Unidata and NSF xml catalogs in IDV
- Date: Tue, 01 Apr 2008 15:17:00 -0600
> Arg!...
>
> *row* major... (no wonder why I am so mixed up on this)
I knew what you meant.
> But thanks for your help earlier.
Glad it's all working for you now. I'll close out the ticket.
Don
> ================================================================
> Bill Capehart <address@hidden> Associate Professor
> Institute of Atmospheric Sciences Land Surface Processes
> 213 Mineral Industries Building Hydrometeorology
> South Dakota School of Mines and Technology Ph: +1-605-394-1994
> 501 East Saint Joseph Street Fax: +1-605-394-6061
> Rapid City, SD 57701-3995 Mobile: +1-605-484-5692
> =================== http://capehart.sdsmt.edu ==================
>
>
> -----Original Message-----
> From: Capehart, William J
> Sent: Tuesday, April 01, 2008 10:22
> To: 'address@hidden'
> Subject: RE: [Support #UPW-774161]: RE: [idvusers] Assistance with Hybrid
> Coordinates (and order of droping data into NetCDF)
>
> Hi Don
>
> Sorry for the long delay in getting back to you on this but I think my head
> is partially on straight now.
>
> I went through my code (IDL and Fortran) and reversed the order in which the
> dimensions are listed in the in the command that creates the commands.
>
> In IDL:
> varid_t = ncdf_vardef(id, 'Temperature', [dim_lon, dim_lat,
> dim_height_above_ground_t, dim_time], /float)
>
> In Fortran90ish:
> dims_4d = (/ x_dimid, y_dimid, z_dimid, t_dimid /)
> nf90_def_var(ncid, "geopotential_height", NF90_FLOAT, dims_4d, varidz)
>
> And now things work. The trouble was that no matter where I looked in the
> fortran and idl (both col major) that I was never able to see the warning
> about reversing the order.
>
> My graphics now have the correct order and I think we're fine, though I
> really wish when the wrote the netCDF programming interfaces, they
> "internalized" the col/row issues for thickies like me.
>
> ================================================================
> Bill Capehart <address@hidden> Associate Professor
> Institute of Atmospheric Sciences Land Surface Processes
> 213 Mineral Industries Building Hydrometeorology
> South Dakota School of Mines and Technology Ph: +1-605-394-1994
> 501 East Saint Joseph Street Fax: +1-605-394-6061
> Rapid City, SD 57701-3995 Mobile: +1-605-484-5692
> =================== http://capehart.sdsmt.edu ==================
>
> -----Original Message-----
> From: Unidata IDV Support [mailto:address@hidden]
> Sent: Friday, February 15, 2008 04:25
> To: Capehart, William J
> Cc: address@hidden
> Subject: [Support #UPW-774161]: RE: [idvusers] Access to the Unidata and NSF
> xml catalogs in IDV
>
> Hi Bill-
>
> > I will try that later today. As for the backwards ordering I'm a little
> > confused. The CF conventions were telling me to do it so that an array was
> > (T, Z, Y, X) and the CF diagnostic script said that it was OK. Is IDV
> > expecting a different order for TZYX?
>
> No, that's what we are expecting, but your file looks like:
>
> float Temperature(nx_lon=50, nx_lat=50, nz_height_above_ground_t=15,
> nt_time=9);
> :long_name = "Temperature @ height_above_ground";
> :units = "K";
> :standard_name = "air_temperature";
> :coordinates = "time height_above_ground_t lat lon";
> :maxvalue = 301.2f; // float
> :minvalue = 200.0f; // float
> float Geopotential_height_surface(nx_lon=50, nx_lat=50);
> :long_name = "Geopotential height @ surface";
> :units = "m";
> :standard_name = "surface_altitude";
> :coordinates = "lat lon";
> :maxvalue = 3017.7f; // float
> :minvalue = 28.1f; // float
>
> which is X,Y,Z,T and X,Y
>
> I would expect them to look like:
>
> float Temperature(nt_time=9, nz_height_above_ground_t=15,, nx_lat=50,
> nx_lon=50);
> :long_name = "Temperature @ height_above_ground";
> :units = "K";
> :standard_name = "air_temperature";
> :coordinates = "time height_above_ground_t lat lon";
> :maxvalue = 301.2f; // float
> :minvalue = 200.0f; // float
> float Geopotential_height_surface(nx_lat=50, nx_lon=50);
> :long_name = "Geopotential height @ surface";
> :units = "m";
> :standard_name = "surface_altitude";
> :coordinates = "lat lon";
> :maxvalue = 3017.7f; // float
> :minvalue = 28.1f; // float
>
> Don
>
>
> Ticket Details
> ===================
> Ticket ID: UPW-774161
> Department: Support IDV
> Priority: Normal
> Status: Open
>
>
Ticket Details
===================
Ticket ID: UPW-774161
Department: Support IDV
Priority: Normal
Status: Closed