[Insight-developers] AnaluzeImageIO filename extensions

[Julien Jomier]

Hans,

Thanks a lot for the explanations.
I've checked in a fix for the problem reported on the users list.

Julien

Hans Johnson wrote:
> Julien,
> 
> It really needs to look for the following:
> .hdr    (I'd guess 60% of the time this is what users will supply)
> .img.gz (I'd guess 21% of the time this is what the user will supply)
> .img    (I'd guess 19% of the time this is what the user will supply)
> 
> Compressed .hdr files are not supported by ITK.  It is not that big of a
> deal, because the .hdr files are always only 384 bytes long.
> 
> Thanks,
> Hans
> 
> PS:  In 6 months or so, we hope to incorporate the NiFtI file format.  This
> is meant to be a first step at a cross functional imaging tool format (SPM,
> fsl, afni, fmristat...).  Unfortunatly, it is based off the Analyze file
> format and is about 95% compliant, 5% non-compliant and uses the same file
> extensions.  We hope that all the non-compliant parts can be reconciled and
> the current itkAnalyzeFileIO class will be able to handle both formats
> appropriately.
> 
> 
> 
> -----Original Message-----
> From: Julien Jomier [mailto:jjomier at cs.unc.edu] 
> Sent: Sunday, January 09, 2005 10:12 AM
> To: hans-johnson at uiowa.edu
> Cc: insight-developers at public.kitware.com
> Subject: Re: [Insight-developers] AnaluzeImageIO filename extensions
> 
> Hi Hans,
> 
> Thanks for the quick reply.
> To make things clear, what filename should set a typical user when using 
> the itkImageFileReader/Writer? (.hdr only?). I mean, can we restrict the 
> AnalyzeIOMethod to this extension only in the CanRead() function? (if 
> yes, this should speedup the IO process a little bit).
> 
> Julien
> 
> Hans Johnson wrote:
> 
>>Julien,
>>
>>The analyze file format is actually a collection of files with the same
>>basename.  The file extensions are for optional image components:
>>
>>.hdr - A required file that contains meta-data information and image
>>dimensions/resolutions/datatype/orientation
>>[.img|.img.gz] - A required* raw datafile that is uncompressed
>>.lkup - NOT IMPLEMENTED IN ITK YET  a simple RGB color index file
>>.obj  - NOT IMPLEMENTED IN ITK YET  a run-length encoded file that is a
> 
> code
> 
>>image to define segemented regions of the image.
>>
>>*It has become very common practice to compress .img image with gzip
>>compression, so we have allowed .img.gz as an extension.
>>
>>Regards,
>>Hans
>>
>>
>>
>>-----Original Message-----
>>From: insight-developers-bounces at itk.org
>>[mailto:insight-developers-bounces at itk.org] On Behalf Of Julien Jomier
>>Sent: Sunday, January 09, 2005 6:21 AM
>>To: insight-developers at public.kitware.com
>>Subject: [Insight-developers] AnaluzeImageIO filename extensions
>>
>>Hi,
>>
>>I'm trying to fix a bug reported on the user's list regarding 
>>AnalyzeImageIO trying to read a file even if the filename was submitted 
>>as .bmp 
>>
> 
> (http://public.kitware.com/pipermail/insight-users/2005-January/011688.html)
> 
>>The fix is easy but I need to know the possible filename extensions for 
>>the Analyze file format. Currently I've .hdr, .img, .hdr.gz, .img.gz.
>>
>>Is Analyze supporting any other extensions?
>>
>>Thanks,
>>
>>Julien
>>_______________________________________________
>>Insight-developers mailing list
>>Insight-developers at itk.org
>>http://www.itk.org/mailman/listinfo/insight-developers
>>
>>
>>_______________________________________________
>>Insight-developers mailing list
>>Insight-developers at itk.org
>>http://www.itk.org/mailman/listinfo/insight-developers
> 
> 
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers