comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » HDF, netCDF, etc question
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
HDF, netCDF, etc question [message #25724] Fri, 06 July 2001 14:33 Go to next message
ronn is currently offline  ronn
Messages: 123
Registered: April 1999
Senior Member
Hi All,

Which format would be best for a large number of large sequential images
along with ancillary data such as field of view, exposure time, etc?
Discrimators would be things like speed in reading them in, ease to pull out
the images and information.

I don't have a lot of experience with these things so any and all opinions
are welcomed.

Thanks,
Ronn


--
Ronn Kling
KRS, inc.
email: ronn@rlkling.com
"Application Development with IDL"� programming book updated for IDL5.4!
"Calling C from IDL, Using DLM's to extend your IDL code" NEW BOOK!
Shareware and Freeware at: http://www.rlkling.com/
Re: HDF, netCDF, etc question [message #25801 is a reply to message #25724] Mon, 16 July 2001 15:06 Go to previous message
thompson is currently offline  thompson
Messages: 584
Registered: August 1991
Senior Member
Aaron Birenboim <aaron@shimi.swcp.com> writes:

> Craig Markwardt <craigmnet@cow.physics.wisc.edu> wrote:

> : ronn kling <ronn@rlkling.com> writes:

> : * I advocated astronomy's FITS format. Plus: platform independent,
> : metadata is in ASCII, good support in IDL Astronomy Library. Minus:
> : seen as "archane."

> I agree. Its very simple, very "sharable".

> : * Many people seem to swear by Liam Gumley's binary tools. Plus: raw
> : speed and direct access; platform neutral. Minus: low level.

> I dunno about this. But before I advocated a simple, binary format
> tied to a database for metadata. These could be a help here.

I also agree that a combination of a standardized format like FITS and a
separate database containing metadata is a good way to go. For example, the
SOHO project uses FITS files, and is supported by an SQL database (Oracle)
which is populated by scanning the FITS headers.

We've also had good success using a database package written in IDL which does
not require a separate license for an SQL database. This software, known as
the UIT database package, is available as part of the Astronomy User's Library
at

http://idlastro.gsfc.nasa.gov/

At least one of the SOHO instrument teams uses this package to maintain its
catalog, instead of a commercial product like Oracle. One of the major
advantages is that one can distribute the software and database files to
outside users without requiring them to buy anything other than IDL.

William Thompson
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: PV-Wave debugger
Next Topic: FAQ?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:04:11 PDT 2025

Total time taken to generate the page: 0.00578 seconds