[vtkusers] vtkTiffWriter does not write 3d volume

[David Gobbi]

Hi Richard,

I would highly recommend that whoever works on the vtkTIFFWriter
looks at the ITK code to see what code could be re-used.  It sounds
like both you and Matheus have a strong interest in adding this
functionality, would it be possible for you to work together on this?

  David



On Thu, Jun 5, 2014 at 1:38 AM, Richard Whitehead <
richard.whitehead at vivosight.com> wrote:

> David,
>
> My experience is that the ITK filters work very well, can we steal code
> from there?
>
> Many thanks,
>
> Richard
>
>
> On 5 June 2014 05:03, David Gobbi <david.gobbi at gmail.com> wrote:
>
>> Hi Richard,
>>
>> VTK already uses libtiff. Matheus has been looking into adding
>> the libtiff calls to the writer that will allow it to write 3D files.
>>
>> Even with libtiff, writing 3D tiff files is not straightforward.  TIFF
>> has many mutually-incompatible ways of storing 3D data:
>> 1) multi-page TIFF
>> 2) tiled TIFF
>> 3) Zeiss' 3D TIFF (non-standard, proprietary)
>> 4) SGI's 3D TIFF (non-standard, proprietary)
>>
>>  - David
>>
>>
>> Unfortunately, TIFF provides provides two standard ways, and
>> several non-
>>
>>   David
>>
>>
>>
>>
>> On Wed, Jun 4, 2014 at 12:28 PM, Richard Whitehead
>> <richard.whitehead at vivosight.com> wrote:
>> >
>> > Marcus,
>> >
>> > I understand libtiff has a good reputation and VTK can be made to use
>> it,
>> > have you tried this?
>> >
>> > Many thanks,
>> >
>> > Richard
>> >
>> >
>> > -----Original Message----- From: Marcus D. Hanwell
>> > Sent: Wednesday, June 04, 2014 5:22 PM
>> > To: Richard Whitehead
>> > Cc: VTK Users
>> > Subject: Re: [vtkusers] vtkTiffWriter does not write 3d volume
>> >
>> >
>> > Richard, Matheus,
>> >
>> > I made several volume related updates to the TIFF reader in VTK
>> > master, but had little need for writing (added support for 32 bit
>> > float, accelerated volume reading times). It would be great to bring
>> > them back into parity, I can point to the relevant commits in the
>> > reader. I will see if I can get to the writer, but make no promises on
>> > timescale as it is not a priority in my current project.
>> >
>> > Thanks,
>> >
>> > Marcus
>> >
>> > On Wed, Jun 4, 2014 at 12:11 PM, Richard Whitehead
>> > <richard.whitehead at vivosight.com> wrote:
>> >>
>> >> Matheus,
>> >>
>> >> I used ITK instead!  This was OK as a workaround for me since I was
>> >> processing files to produce other files; but when the data is in
>> memory it
>> >> will not be a good solution.
>> >>
>> >> Richard
>>
>
>
>
> --
>
> Richard Whitehead *-* Senior Imaging Engineer
>
> *Michelson Diagnostics Ltd*
>
> *M:* +44 (0)7905 955276   *T:* +44 (0)20 8308 1695
>
> *E: *richard.whitehead at vivosight.com   *W:* www.vivosight.com
>
>
> <http://www.vivosight.com/>
>
>
> Michelson Diagnostics Ltd, 1 Grays Farm Production Village, Grays Farm
> Road, Orpington, Kent  BR5 3BD, UK
>
> Registered Office: 3 Shearwater, Maidstone, ME16 0DW.     Registered in
> England No. 5732681
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20140605/e15c42ea/attachment-0001.html>