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

[AWIPS #PUI-232297]: NOAAPort

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: [AWIPS #PUI-232297]: NOAAPort
  • Date: Wed, 09 Nov 2016 13:44:24 -0700

NOAAport ingest is outside of my domain, so I can't be of much help.  I did 
find these docs 
https://www.unidata.ucar.edu/software/ldm/ldm-current/utilities/noaaport/index.html

And you can always write in to address@hidden to ask about this. 

-mj


> I meant receiving data into the LDM using NOAAPort as the primary data source 
> instead of the Unidata IDD. I didn’t know if I needed any special flags when 
> installing the LDM portion of the AWIPS software to signal it to use to the 
> NOAAPort channels or if it was a simple change in the ldmd.conf file as you 
> mentioned.
> 
> 
> > On Nov 9, 2016, at 3:22 PM, Unidata AWIPS Support <address@hidden> wrote:
> >
> >> Unidata:
> >>
> >> Does anything specific need to be changed in the AWIPS 2
> >> installation/configuration in order to link to NOAAPort versus the
> >> Unidata IDD?
> >
> >
> > What do you mean by "link to"?  Data comes into the system via the LDM 
> > which points to an upstream server, so you are able to simply change the 
> > address in ldmd.conf.  If you're asking about ingesting data into EDEX 
> > directly from a noaaport receiver, I can't answer that.
> >
> > -mj
> >
> > Ticket Details
> > ===================
> > Ticket ID: PUI-232297
> > Department: Support AWIPS
> > 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.
> >
> >
> 
> 

Ticket Details
===================
Ticket ID: PUI-232297
Department: Support AWIPS
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.