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

[NOAAPORT #BGK-918302]: NOAAPort ingest not working

Hi,

re:
> You have given me the critical information I needed to tackle the problem.

This sounds promising!

re:
> So much happened last weekend. As I have mentioned in my previous email, we 
> are
> in the process of configuring three new servers to replace our two legacy 
> servers. We
> started configuring LDM on one of the new production servers. Since I am not 
> a super
> user on that specific server, I had to rely on IT to make configuration 
> changes on the
> new LDM server. I requested a root access on all new servers, but I got on 
> only one (the
> one we didn't install LDM) and while nagging IT to give me root access on the 
> other
> ones, I decided to install and configure ldm on the server that I have root 
> access on.

Very good.  I trust that went well?

re:
> The three servers are exactly the same, which makes easier on configuration 
> of software
> tools. Long story short, I installed and configured LDM on that server. Then 
> I added the
> routes, stopped the firewall (because the interface is dedicated for noaaport 
> and other
> traffic is controlled at domain level), I added the necessary ports and rules 
> at the
> iptables and noaaport data started flowing.

This is very good news indeed.  I have questions:

- exactly what did you do for "I added the routes"

  I.e., did you use the example I sent, or did you try to replicate what was on
  your old system?

- stopped the firewall

  OK.  Can I assume that IPTABLES was not running?

- "I added the necessary ports"

  Exactly how did you do this and where?

re:
> I have also added the routes for the GOES-R
> feeds and added the ingest lines on ldmd.conf.

This makes it sound like you are still doing the route for individual
feeds.  I think that it is much more efficient to do it for all of
the feeds (as per the 'route add' command I sent earlier).

re:
> However, I run into this link, which is
> quite recent and I want to ask your advice on the configuration.
> 
> https://www.unidata.ucar.edu/blogs/news/entry/service-update-changes-to-the

Yes, this is the announcement of our revamping the IDD NIMAGE datastream (not
the one created by NOAAPort ingesters) by sending images that have been 
reconstituted from the tiles sent in NOAAPort.  This centralizes the process
for restitching the tiles, and makes the overall use of the data simplier
(in my opinion, at least).

re:
> My question is, is it better to get the GOES-R data through the noaaport feed 
> or the
> unidata  idd.unidata.ucar.edu?

Since you are not a Unidata university, you would need to get an IDD relay of
the revamped NIMAGE feed that is in the IDD in order to use the data we are
sending in the revamped NIMAGE feed.

re:
> From the above link it looks like unidata stiches all
> the images and sends it as complete product.

Correct.

re:
> Right now we are using new version of
> gempak as the analysis and display software but I found AWIPS to be very 
> interesting
> tool. 

One GEMPAK user reported a problem with using the new images in GEMPAK.
This is being investigated.  Other packages that we make available,
AWIPS, McIDAS-X (for universities only), the IDV and MetPy all work
well with the new images.

re:
> If you could give me your recommendation on the best way to get GOES-R data 
> that
> would be great.

Are you working with a university that is connected to the IDD to get feeds?
If yes, is that/those university(ies) getting the revamped NIMAGE feed?

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: BGK-918302
Department: Support NOAAPORT
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.