On Tue, Apr 26, 2011 at 20:31, Daniel Lepage wrote:
> You need PIL no matter what; scipy.misc.imread, scipy.ndimage.imread,
> and scikits.image.io.imread all call PIL.
I believe there are two pure python readers:
http://code.google.com/p/pylibtiff/
http://www.lfd.uci.edu/~gohlke/code/tifffile.py.
On Tue, Apr 26, 2011 at 9:09 PM, Mathew Yeates wrote:
> is scikits.image.io documented anywhere?
http://stefanv.github.com/scikits.image/api/scikits.image.io.html
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman
is scikits.image.io documented anywhere?
On Tue, Apr 26, 2011 at 11:45 AM, Zachary Pincus
wrote:
>
> On Apr 26, 2011, at 2:31 PM, Daniel Lepage wrote:
>
>> You need PIL no matter what; scipy.misc.imread, scipy.ndimage.imread,
>> and scikits.image.io.imread all call PIL.
>
> scikits.image.io also
On Apr 26, 2011, at 2:31 PM, Daniel Lepage wrote:
> You need PIL no matter what; scipy.misc.imread, scipy.ndimage.imread,
> and scikits.image.io.imread all call PIL.
scikits.image.io also has a ctypes wrapper for the freeimage library.
I prefer these (well, I wrote them), though apparently the
On Tue, Apr 26, 2011 at 8:31 PM, Daniel Lepage wrote:
> You need PIL no matter what; scipy.misc.imread, scipy.ndimage.imread,
> and scikits.image.io.imread all call PIL.
Scikits.image has a plugin system for IO and can use FreeImage to load
images. PIL's Tiff image handling is pretty buggy (espec
You need PIL no matter what; scipy.misc.imread, scipy.ndimage.imread,
and scikits.image.io.imread all call PIL.
Theoretically there's no difference between any of them, although in
actuality some use "import Image" and others use "from PIL import
Image"; one of these may fail depending on how you
Hi
What is current method of using ndiimage on a Tiff file? I've seen
different methods using ndimage itself, scipy.misc and Pil.
Mathew
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
