Hi Carol,
re: running a version of ncdump that gets built with McIDAS
>
> %which ncdump
> /home/mcidas/bin/ncdump
OK, thanks for the info.
re:
> This machine is running the version of 'ncdump' that gets built as part of
> a McIDAS installation.... hum
That version should have worked fine.
re:
> I used a different machine to run an ncdump. I was see that a lot of the
> data at the beginning is zero, but then there are a lot of other values.
This is to be expected if you are copying an entire image and the image
is a full disk scan since there will be a lot of space in the scan.
re:
> Is there anything I should specifically check using ncdump? The header is
> the following, and I think that looks good.
>
> netcdf meteosat-11.201808282015.03I {
> dimensions:
> xc = 3712 ;
> yc = 3712 ;
> time = 1 ;
> auditCount = 3 ;
> auditSize = 80 ;
> variables:
> int version ;
> version:long_name = "McIDAS area file version" ;
> int sensorID ;
> sensorID:long_name = "McIDAS sensor number" ;
> int imageDate ;
> imageDate:long_name = "image year and day of year (in ccyyddd format)" ;
> int imageTime ;
> imageTime:long_name = "image time in UTC (hours/minutes/seconds, in HHMMSS
> format)" ;
> int startLine ;
> startLine:long_name = "starting image line (in satellite coordinates)" ;
> int startElem ;
> startElem:long_name = "starting image element (in satellite coordinates)" ;
> int time(time) ;
> time:long_name = "seconds since 1970-1-1 0:0:0" ;
> time:units = "seconds since 1970-1-1 0:0:0" ;
> int dataWidth ;
> dataWidth:long_name = "number of 8-bit bytes per source data point" ;
> int lineRes ;
> lineRes:long_name = "resolution of each pixel in line direction" ;
> lineRes:units = "km" ;
> int elemRes ;
> elemRes:long_name = "resolution of each pixel in element direction" ;
> elemRes:units = "km" ;
> int prefixSize ;
> prefixSize:long_name = "line prefix size in 8-bit bytes" ;
> int crDate ;
> crDate:long_name = "image creation year and day of year in ccyyddd format" ;
> int crTime ;
> crTime:long_name = "image creation time in UTC in hhmmss format" ;
> int bands ;
> bands:long_name = "satellite channel number" ;
> char auditTrail(auditCount, auditSize) ;
> auditTrail:long_name = "audit trail" ;
> float data(time, yc, xc) ;
> data :long_name = "Raw Satellite Counts" ;
> data :type = "MSG " ;
> data :coordinates = "lon lat" ;
> float lat(yc, xc) ;
> lat:long_name = "lat" ;
> lat:units = "degrees_north" ;
> float lon(yc, xc) ;
> lon:long_name = "lon" ;
> lon:units = "degrees_east" ;
>
> // global attributes:
> :Conventions = "CF-1.4" ;
> :Source = "McIDAS Area File" ;
> :Satellite\ Sensor = "METEOSAT11 " ;
> }
This all looks OK to me.
To check the netCDF file, I would try displaying the image in it using
an application that works with netCDF as input, something like the
IDV.
re:
> Thanks again for your help today!
No worries.
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: LSJ-196213
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.
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.