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

[conduit] Spotty NAM

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: [conduit] Spotty NAM
  • Date: Sat, 29 Mar 2014 19:54:41 -0400
 
Over the last few runs, I've noticed that CONDUIT NAM has been short quite a few fields at various forecast hours. Since I pull NAM off of my NOAAPORT feed, I don't always notice when fields are missing, but it's severe weather season and some helicity fields are only available on the CONDUIT stream. Surprised smile
 
Has anyone else noticed this issue?
 
Here is a graphic that compares NAM products coming directly off my dish, and those with the DISH + CONDUIT backup:
 
 
Notice that NOAAPORT NAM seems just fine, but CONDUIT + NOAAPORT have issues. F000-F18 seems ok, then spotty, then F027 + F 039 seem ok, then the rest have issues all the way through.
 
Maybe we can get grid number 59 added to noaaport? Smile
 
cheers,
 
--patrick
 
--
----------------------------------------
Patrick L. Francis
Vice President of Research & Development
Media Logic Group

http://www.medialogicgroup.com
http://www.hamweather.com
http://www.alertsbroadcaster.com
http://www.modelweather.com

FB: http://www.facebook.com/wxprofessor

----
_______________________________________________
conduit mailing list
address@hidden
For list information or to unsubscribe, visit: 
http://www.unidata.ucar.edu/mailing_lists/