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

[Datastream #JGQ-332966]: Viewing Global Mosaic Sat Files

Hi,

re:
> I recently received the TICF* Global Satellite Composites from the
> NOAAPort data stream (NOTHER feed) via LDM. Upon receiving these files
> that are supposed to be in NetCDF format, I tried to view the files
> using ncdump to view the contents, but it is unable to read them. Are
> the files correctly encoded when using LDM, or is this possibly due to
> the formatting of the files themselves?

The GOES products sent in NOAAPort have a broadcast header, typically 32 bytes
long, added to the beginning of each product.  This header must be stripped
before the rest will look like a netCDF file.

Here is what I did to strip the header and then verify that the product is,
in fact, a netCDF file:

$ dd bs=32 skip=1 if=TICF08_131600_25253555.nc 
of=TICF08_131600_25253555_trimmed.nc
103585+1 records in
103585+1 records out
3314722 bytes (3.3 MB, 3.2 MiB) copied, 11.1156 s, 298 kB/s

$ ls -alt
total 6475
-rwxrwxrwx. 1 root root 3314722 Sep 13 12:36 TICF08_131600_25253555_trimmed.nc
drwxrwxrwx. 1 root root       0 Sep 13 12:36 .
drwxrwxrwx. 1 root root       0 Sep 13 12:32 ..
-rwxrwxrwx. 1 root root 3314754 Sep 13 11:28 TICF08_131600_25253555.nc

$ od -c TICF08_131600_25253555_trimmed.nc | less

$ ncdump -h TICF08_131600_25253555_trimmed.nc 

netcdf TICF08_131600_25253555_trimmed {
dimensions:
        time = 1 ;
        yc = 3000 ;
        xc = 4999 ;
variables:
        float data(time, yc, xc) ;
                data:long_name = "0-255 Brightness Temperature" ;
                data:type = "VISR" ;
                data:coordinates = "lon lat" ;
                data:_FillValue = -9999.f ;
                data:units = "none" ;
        float lat(yc, xc) ;
                lat:long_name = "lat" ;
                lat:units = "degrees_north" ;
                lat:_FillValue = -9999.f ;
                lat:valid_range = -90.f, 90.f ;
                lat:standard_name = "latitude" ;
        float lon(yc, xc) ;
                lon:long_name = "lon" ;
                lon:units = "degrees_east" ;
                lon:_FillValue = -9999.f ;
                lon:valid_range = -180.f, 180.f ;
                lon:standard_name = "longitude" ;
        int time(time) ;
                time:long_name = "seconds since 1970-1-1 0:0:0" ;
                time:units = "seconds since 1970-1-1 0:0:0" ;

// global attributes:
                :Conventions = "CF-1.4" ;
                :Source = "McIDAS Area File" ;
                :Satellite\ Sensor = "DERIVED DATA" ;
                :time_coverage_start = "2023-09-13T15:00:00" ;
                :instrument_name = "GLOBCOMPWV" ;
                :history = "Wed Sep 13 15:34:16 2023: ncks -d xc,0,4998 
tempwv.nc outwv.nc" ;
                :NCO = "netCDF Operators version 4.7.5 (Homepage = 
http://nco.sf.net, Code = http://github.com/nco/nco)" ;
}

Comment:

- I setup a 'notifyme' invocation on one of our NOAAPort ingest machines to see 
if we are
  receiving TICF products:

  notifyme -vl- -p TICF -o 3600

  and have let it run for over an hour now without seeing any TICF products.

Question:

- are you receiving TICF products in your LDM feed now, or was the product
  you attached an one-off?

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: JGQ-332966
Department: Support Datastream
Priority: Normal
Status: Open
===================
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.