[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDD #AAI-197813]: Unidata ldm feeds for Alaskan metar & maritime data
- Subject: [IDD #AAI-197813]: Unidata ldm feeds for Alaskan metar & maritime data
- Date: Fri, 02 Nov 2018 08:31:12 -0600
Hi Carl,
re:
> I am with the University of Alaska Fairbanks at the Geographic Information
> Network of Alaska (GINA). As a polar satellite Direct Broadcast facility,
> we use LDM heavily to distribute satellite products from our office to the
> National Weather Service. We also receive satellite data via LDM from our
> developer partners at other locations.
Excellent! :-)
re:
> We have our own AWIPS/EDEX set up
> that is modelled after the configuration at Alaskan NWS offices.
Very good.
re:
> Is there
> a Unidata LDM feed that we could subscribe to that would enable us to
> receive Alaskan metar and maritime observations in our AWIPS?
Yes. The feed type is "IDS|DDPLUS", and you can REQUEST the feed from
either/both of the top level IDD relays that we operate here in UCAR:
idd.unidata.ucar.edu
iddb.unidata.ucar.edu
The "IDS|DDPLUS" feed is populated with the textual products that are
distributed by the NWS in the NOAAPort SBN.
re:
> If so, what would be involved in setting that up?
If there is forward and reverse DNS for your machine that is running
an LDM, and if its name resolves to a '.edu', then all you need to
do is:
- add a REQUEST line for IDS|DDPLUS to your LDM configuration file,
~ldm/etc/ldmd.conf
- (possibly) add an EXEC line to process the IDS|DDPLUS feed products
Adding an EXEC line would be needed if you create a new pattern-action
file with the actions that you want to be executed.
If your intention is to feed your AWIPS/EDEX machine, then it is most
likely that the actions that would be executed are already in an existing
pattern action file. If this is true, you shouldn't have to add an
EXEC line.
- stop and restart your LDM for the change(s) in the LDM configuration
file to take effect.
The easiest way to test to see if you are ready to go with REQUESTing
feeds from our top level servers is by using the LDM 'notifyme' utility.
Here is an example:
<as 'ldm' on your machine>
notifyme -vl- -f "IDS|DDPLUS" -h idd.unidata.ucar.edu
and/or
notifyme -vl- -f "IDS|DDPLUS" -h iddb.unidata.ucar.edu
Success will be indicated by one of 'notifyme's output lines looking
like:
Nov 02 14:29:13 notifyme[13147] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK
If you get a message that looks like:
Nov 02 14:28:43 notifyme[13475] ERROR: NOTIFYME(idd.unidata.ucar.edu): 7:
Access denied by remote server
the most likely cause would be that reverse DNS (IP -> name) does not
exist for your machine, and you'd need to contact your network folks
to get this setup.
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: AAI-197813
Department: Support IDD
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.