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

[McIDAS #MUB-377647]: Converting MciDAS to NetCDF navagation issue

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: [McIDAS #MUB-377647]: Converting MciDAS to NetCDF navagation issue
  • Date: Thu, 20 Oct 2016 18:08:46 -0600
Hi Dave,

I ran several tests in McIDAS-V to see how the image saved in the netCDF file
you downloaded from NOAA/CLASS compared to the image stored in the AREA file you
also downloaded from NOAA/CLASS.  The tests indicated that the image stored
in the netCDF file that you downloaded from NOAA/CLASS had navigation and
data values that matched the navigation and data values contained in the AREA
file.  My conclusion from these tests is that you should use the netCDF files
you can download from NOAA/CLASS for your case study.  Another reason to
use these files instead of the ones that could be created by AreaToNetcdf.jar
is that those netCDF files contain brightness values (values range from 0
to 255), not raw values (which range from 0 to 19360).

Aside:

I tried to display the image created by AreaToNetcdf.jar in McIDAS-V, but the
file was not CF compliant, so it wouldn't load.  The problem appears to be
in how the latitude and longitude arrays are named (lats and lons instead of
lat and lon).  I will try to fix up the variables in the netCDF file to be 
(more)
CF compliant using NCML tomorrow just so I can see how much of a difference 
there
is between the image from the AREA and the image from the 
AreaToNetcdf.jar-created
netCDF file.

I hope that this helps...

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: MUB-377647
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with 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.