Hi Rodrigo,
I apologize for the slow reply. I am currently in Burkina Faso (Africa) where
conference activities and slow/non-existent network connections have severely
hindered my ability to respond to emails...
> Steve answered me yesterday !...
> But still have some questions.. I wrote him this morning ...
> I don't have any "gini" file below /home/ldm/gempak/images/sat/..
> I have only "area" files and they are ok... but, I have installed
> a thredds server last week.. Our final goal is to use idv and data
> from ldm server ( and our own locally generated data (models, etc..))
> for academic stuff ... last year we have used Gempak, but may be
> IDV is a little bit more friendly for the students here ..
OK, I understand.
GINI imagery is available in two different IDD datastreams: FNEXRAD and
NIMAGE, and the FNEXRAD feed contains some imagery in GINI format, and
some in AREA format.
The pqact.conf action you sent in your first email (to ldm-users)
contained an action for imagery in the UNIWISC (aka MCIDAS) datastream.
It is, therefore, likely that you are not decoding GINI images because:
- you are not requesting the data in your ~ldm/etc/ldmd.conf file
- if you are requesting the data, you do not have decoding actions
in your ~ldm/etc/pqact.conf file(s)
For reference, ldmd.conf request lines for data in GINI format would
look something like:
request FNEXRAD ".*" idd.unidata.ucar.edu
request NIMAGE ".*" idd.unidata.ucar.edu
(Just so you know, if you request all of the NIMAGE data, you will receive
a LOT of data every hour. Also, the imagery in the NIMAGE feed only covers
North America, Puerto Rico, Alaska, and Hawaii. It does not extend further
south than about 20N latitude, so it will be of little interest for
users in Chile.)
Example pqact.conf actions to process these data would look something like:
#########################################################################
#
# FNEXRAD section
#
# PNG compressed 1km radar GINI format
FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....)
PIPE -close
decoders/pngg2gini -vl logs/ldm-mcidas.log
data/gempak/images/sat/RADAR/\1/\2/\2_\3_\4
# NEXRCOMP 6 km National BREF mosaic in AREA format
FNEXRAD ^pnga2area Q5 (RL) (.*) (.*) (.*) (.*) (........) (....)
PIPE -close
decoders/pnga2area -vl logs/ldm-mcidas.log
data/gempak/nexrad/NEXRCOMP/6KN0R-NAT/\4_\6_\7
# NEXRCOMP 1 km Regional BREF mosaic in AREA format
FNEXRAD ^pnga2area Q5 (RO) (.*) (.*) (.*) (.*) (........) (....)
PIPE -close
decoders/pnga2area -vl logs/ldm-mcidas.log
data/gempak/nexrad/NEXRCOMP/1KN0R-FLT/\4_\6_\7
# NEXRCOMP 10 km National RCM mosaic in AREA format
FNEXRAD ^pnga2area Q5 (RN) (.*) (.*) (.*) (.*) (........) (....)
PIPE -close
decoders/pnga2area -vl logs/ldm-mcidas.log
data/gempak/nexrad/NEXRCOMP/10KRCM-NAT/\4_\6_\7
#########################################################################
#
# NIMAGE Actions
#
# Zlib compressed NOAAPORT GOES-East/West GINI images
NIMAGE ^satz/ch[0-9]/.*/(.*)/([12][0-9])([0-9][0-9])([01][0-9])([0-3][0-9])
([0-2][0-9])([0-
5][0-9])/(.*)/(.*km)/
PIPE -close
decoders/zlibg2gini -vl logs/ldm-mcidas.log
data/gempak/images/sat/\8/\9/\1/\1_\2\3\4\5_\6\7
> Thank you for your help ...
No worries.
I am curious about why you want to ingest and serve the NIMAGE images given that
they do not cover any portion of South America. Is your objective to serve
all of the data possible as a test?
I am travelling back to the US today (it takes a full day), so I will not
be reading email again until Monday.
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: OPC-671989
Department: Support ldm-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.