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

[ldmMcidas #XGX-360555]: decoding FNEXRAD 1 km N0R composite images

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: [ldmMcidas #XGX-360555]: decoding FNEXRAD 1 km N0R composite images
  • Date: Fri, 10 Aug 2007 06:39:33 -0600
Hi Elmer,

re: please send the output of DSSERVE for both input and output
datasets

> dsserve.k LIST RDA
> 
> Group/Descriptor         Type  Format & Range     RT Comment
> ------------------------ ----- ------------------ -- --------------------
> RDA/1KMBREF              IMAGE AREA 8001-8050


This is fine for the output dataset.

> dsserve.k LIST LOC
> 
> Group/Descriptor         Type  Format & Range     RT Comment
> ------------------------ ----- ------------------ -- --------------------
> LOC/MD                   POINT MD   1-9999
> LOC/NLDN                 POINT MD   1101-1148
> LOC/POS                  IMAGE AREA 1-9999

This is your problem.  The input file is _not_ a McIDAS AREA; it is
a NOAAPORT GINI image.  Your input dataset, LOC/POS, tells McIDAS
to read the image as if is an AREA.

What you can do is:

- rename AREA8000 to something else like:

  mv AREA8000 composite_20070810_1036

  There is nothing wrong about using AREA8000 since McIDAS doesn't care
  about the names of files per se.  It is, however, a good idea to
  use the convention that files named AREAnnnn (nnnn ranges from 0001 to 9999)
  contain images in McIDAS AREA format.  This will prevent confusion down
  the road.

- create a dataset of type GINI

dsserve.k ADD LOC/GINI GINI TYPE=IMAGE DIRFILE=composite_* \"Unidata Nexrad 
Level III N0R composite

- copy from the input GINI dataset to the output AREA dataset.  This will
  do the format conversion:

imgcopy.k LOC/POS.1 RDA/1KMBREF.1 SIZE=ALL

This should create the file AREA8001.

I suspected this kind of mistake when you named the output of pngg2gini 
AREA8000.

> The use of AREA8000 was a lift from the shell script to invoke the
> unisys decoder for our old data feed. It was $bin_dir/unisys2area
> AREA9001 $newfile AREA8000 REF then an imgcopy.k LOC/POS.8000
> RDA/2KMBREF SIZE=ALL to put the finished product in place.  No idea what
> the AREA9001 did, but $newfile is the raw data input, AREA8000 is a
> dummy holding area.

AREA8000 may be a dummy holding area, but your LOC/POS dataset says it
is of type AREA which it is not.

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: XGX-360555
Department: Support ldm-mcidas
Priority: Normal
Status: Closed