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

Re: Acceptable input formats for NCAR IDV

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: Re: Acceptable input formats for NCAR IDV
  • Date: Fri, 6 Dec 2013 13:07:22 -0700

Hi Alva,

The cf conventions for "discrete sampling geometries" were developed with that sort of data in mind.  It's good to remember that we have large collections of weather and buoy and other station data in the atmospheric realm as well.  That said, the idv has been developed for integrating data from many dispirate sources so it is pretty flexible in terms of input protocols and formats.  That is probably why it is not easy to pin down concisely.  So I'm forwarding this to the idv team for a more definitive response.

--Ben

On Dec 6, 2013 12:24 PM, "Alva Couch" <address@hidden> wrote:
Ben,

I and Yaping Xiao are trying to create a data format that is an output
of the CUAHSI data system and suitable for input to the NCAR IDV. We
are having trouble finding documentation on the input format
accepted by the IDV. We are working from the only document that we
can find, which is the CFPoint documentation.

Currently we have having to resort to reverse engineering of documented
IDV sources that generate compliant code.

Is there better documentation of how to construct an IDV input
to represent station time series? Could you help us find it?

Many thanks,
- alva


--
Dr. Alva L. Couch
Associate Professor of Computer Science
Tufts University, Medtord, MA 02155