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 Kelly, re: > The Florida State University idd site information changed a couple > of years ago. > > http://www.unidata.ucar.edu/projects/idd/sitelist.html OK, thanks for letting us know. re: > Here are our new contacts. > > Kelly Hirai > address@hidden > 850-644-1550 > > Edward Peirce > address@hidden > 850-644-2522 > > pluto.met.fsu.edu is still our ldm ingester. I updated the site contact list page with the new information. Question: - is address@hidden still a viable email address for downstream users to send questions about the feed(s) they are getting/want to get from pluto.met.fsu.edu? If not, I will remove it from the site administrator list. re: > Also, i'm pretty sure Jordan Yao is not longer at COAPS. My guess is its > > Michael McDonald > address@hidden > 850-645-7462 > > But i would get with him to be sure that is right. OK, thanks for this info. I see that you CCed Michael on this email, so we will wait to hear from him as to whether he should be listed as the LDM/IDD contact for the Center for Ocean-Atmosphere Prediction Studies (COAPS). re: > Finally, i am looking for goes-r realtime satellite imagery. we used to > have a satellite box that ingested the NOAAPort signal from a tap off > the co-located KTLH NWS station dish but that box went out about 6 years > ago. there is interest in reviving that unit. you have any hints on what > it would take? Our NOAAPort ingest software was bundled as part of the LDM a few years ago. If KTLH's NOAAPort ingest is active, then you should be able to tap off of the UDP stream from their Novra S300N DVBS2 receiver; feed it into an Ethernet interface that is dedicated for NOAAPort ingest on one of your machines; build, install and configure the NOAAPort component of a current LDM installation; and then once again be ingesting the data flowing in the NOAAPort Satellite Broadcast Network (SBN). If KTLH does not have an active NOAAPort ingest but you still have a tap into a satellite dish that is pointed at the NOAAPort satellite, then you would need to purchase a DVBS2 receiver like the Novra S300N and connect the tap off of the dish to the input side of the receiver. From there, the procedure would be the same as I outlined. If you do not want to re-enter the NOAAPort ingest "game", and assuming that your network bandwidth is sufficient, then you could simply REQUEST all of the NOAAPort-derived IDD feeds that have the data you are looking for (e.g., IDS|DDPLUS, HDS, NGRID, NEXRAD3, NIMAGE, NOTHER. The NOTHER feed contains the GOES-16 imagery that is being sent down as a series of tiles for each coverage (e.g., FullDisk, CONUS, Puerto Rico, Mesoscale-[12]) currently in the feed. Your job would then be to stitch together the tiles into full scenes and use them accordingly. FYI: the tiles and the full scenes created from tiles will both be in netCDF-4 files. Also, we put together some Python scripts that can stitch the tiles back into full scenes and make it (along with a LOT of other things) available in the Unidata area of github. 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: UHR-178326 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.