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

20040609: DVB readnoaaport software

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: 20040609: DVB readnoaaport software
  • Date: Thu, 10 Jun 2004 18:18:03 -0600
>From: Todd Smith <address@hidden>
>Organization: SSEC
>Keywords: 200406082218.i58MIStK019044 NOAAPORT XCD

Hi Todd,

>XCD heads up:  We found that the XCD grid decoder does not include a 
>change that you made a year or two ago to fix some NCEP Vs. ECMWF grid 
>confusion.  We had to back out of it then because it broke our ECMWF 
>grid ingest.  The problem only crops up on high res grids coming in from 
>the CONDUIT feed so we didn't notice it during our testing.  We're 
>testing your fix (Mcmkmcgrid.f) and will be releasing an addendum very soon.

Here is another heads up for XCD:  sigco.pgm does an include of
m0xcd.inc before it does an 'implicit none'.  Since m0xcd.inc declares
types of variables, it will cause a compilation error on some platforms
when built with gcc/g77.  The solution is simple: move the include to
after the 'implicit none'.

On a related topic...  What is _really_ needed in XCD is:

- being able to name output files in a non-standard manner.  Here are
  two examples:

  20040611_sfc.md     - instead of MDXX0003
  20040611_gfs_12.gid - instead of GRIDnnnn

  This is doable now that DSSERVE can create MD and GRID datasets using
  DIRFILE=.  The beauty of this is that it would get rid of the
  incredibly hard to understand RTMODELS.CFG file.

- the ability of XCD to decode GRIB2 model data (this is a biggie!)

- data compression in decoded GRID files

Anybody thinking about things like this?  :-)

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.