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.
Hi Marck, I just noticed that I inadvertently overlooked your last message in the exchange we had been having about NMHS being fed textual data available in the Unidata IDD. I apologize for this oversight! re: > Maybe we should just try the text data and see how it goes. The global observation data (textual data relayed in the LDM/IDD IDS|DDPLUS datastream) is a good starting point for testing how much data you can receive via your 10 Mbps network connection. re: > Gempak seems to be really > more tailored to receive the ids datastream compared to the gifs datastream. "gifs datastream"? I am not sure what this is exactly. re: > I managed to write some scripts to get the wafs grib dataset from wifs and > display it as > gfs in gempak. We are running wrfems also for the local region and that is > ingested > easily in gempak. Therefore I believe I have the model data covered for > gempak purposes. OK. re: > Our Public IP is 206.48.100.225 and is a Static IP Address assigned by our > ISP and we do > not have a DMZ available. We do have a Firewall that is configured with port > forwarding. > NOAA uses the 206.48.100.225 for the SSL VPN. All LDM/IDD dataflows are initiated by the downstream machine. The requirement, therefore, is that the firewall at the downstream's site allow outbound traffic on port 388. I am not sure if your firewall will support that; some simple testing will need to be done to figure out what works and what doesn't. re: > I can assign another static ip also that can be used just for IDS for example > 206.48.100.228. This will be a dedicated unix box outside the firewall. We can setup a special ALLOW for you machine at 206.48.100.228 for testing only. What you will need to do is: - register with the Unidata website - download, build and install the most recent version of the LDM on your *nix machine - after the LDM is installed on your machine, we will then implement a temporary ALLOW for your machine here in Unidata - after the temporary ALLOW is in-place, we will need to work together to determine if a REQUEST from your machine will make it through your firewall Again, many apologies for not responding to you before now! 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: VRK-635010 Department: Support IDD Priority: Critical Status: Closed