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.
Joel, We provide information about CONDUIT under the community cooperating endeavors area of our web pages: http://www.unidata.ucar.edu/data/conduit/ Most recently, we held a meeting in Atlanta during the AMS where additions and changes to the current stream were discussed (pending the lifting of the NWS moratorium). Look at the Atlanta meeting summary links for information about near-term changes which are in progress. You can stay informated about CONDUIT related issues, including changes to the data stream by subscribing to the CONDUIT/C2 mail list. I provide some basic information about the current IDD contents, LDM product identifiers, and monitoring on a link from the above URL: http://www.unidata.ucar.edu/data/conduit/ldm_idd/ As always, you can send questions directly to address@hidden, or post directly to the CONDUIT email list if you have subscribed. Steve Chiswell Unidata User Support > Hi Steve! > > Kelvin sent me in your direction. > > Background. I run the Integrated Radar Data Service (IRaDS) operation > for OU which is changing names to Integrated Robust Assured Data > Services (IRADS). The name change reflects where we're headed. > Commerce and government see a role for us at the university level to > aggregate and position reliable data as a commodity for future > product and service development. We (the university) see that we have > to position data for education and core research anyway, so the > concept here is to take a next step and make the data aggregation and > provisioning "industrial strength" in terms of comprehensiveness, > timeliness, and reliability. > > The CONDUIT data stream will have great value to others in > government, the military, and industry. Kelvin has advised that no > restriction on redistribution exist and we'd like to stage this data > as indicated in the above conceptual model. > > Could you help point us to technical descriptions of the data itself, > particularly in terms of what is available, when it flows, and how we > will know of any changes in the data composition over time? I'm > briefing an industry group tomorrow and if you have some preliminary > briefing information or technical details on the CONDUIT data, it > will be of great value as we launch efforts to incorporate this new > "channel" of information for our clients. > > It's important to note that IRADS is a program of the university > designed to be a top-tier provider of data at cost. We do not charge > for the data itself, just for the provisioning mechanisms that add > robust 24/7 reliability, low latency, and redundancy. > > Thanks in advance for any help you can provide. I've also copied > Carl Sinclair and Curtis Rose who help with IRADS technical matters > as well as Scott Hill who currently helps IRADS and manages CONDUIT > data here for Kelvin. > > > Sincerely, > -- Joel > ---------+---------+---------+---------+---------+--------- > JOEL D. MARTIN, Colonel, USAF (ret.) > � Associate Vice President, Information Commerce > � Sasaki Institute � Director of Marketing and Operations > � Director, Integrated Radar Data Services Program > > The University of Oklahoma > Mail: 350 David L Boren Blvd, Suite 1800, Norman, OK 73072 > Office: Research Campus, 350 David L Boren Blvd, Suite 1650 > Work:(405)325-4574 Mobile:(405)476-0119 Fax:(405) 325-7614 > E-Mail: address@hidden Web/Calendar: http://jdm.ou.edu/ > ---------+---------+---------+---------+---------+--------- > > > Ticket Details =================== Ticket ID: AAQ-434446 Department: Support CONDUIT Priority: Normal Status: Closed