Alasdair McAndrew amc...@gmail.com on Thu, 29 Nov 2012 wrote:
Probably the combinations of OpenCV, Scipy.ndimage and scikits-image
would cover pretty much all of my needs.
Hi,
All of those (+ mahotas, which is the package I wrote imread which
might be useful for microscopy file formats)
Am 28.11.2012 22:11, schrieb Jorgen Grahn:
I thought those formats were dead since about a decade? (Ok, I know
TIFF has niches, but JPEG 2000?)
Baseline TIFF is still used a lot when a lossless image format is
required. It's widely used for scientific stuff, long-time preservation,
health care
Hey Alasdair,
I believe OpenCV might do the trick for you:
- it contains everything you seem to need (+ much much more);
- it is efficient;
- it is cross-platform;
- it has a usable python interface since version 2.4;
- it is not going away any time soon and is constantly improved;
- it has an
Thanks for the heads-up about OpenCV. I have in fact briefly looked at OpenCV
(well, the documentation), and it does seem remarkably complete. And what it
doesn't provide, such as image transforms (FFT, DCT etc), are offered elsewhere
by other Python libraries.
Probably the combinations of
On Wed, 28 Nov 2012 04:30:25 -0800, Alasdair McAndrew wrote:
What I want to know is - what are the current standard libraries for
image processing in Python which are in active development?
NumPy/SciPy.
PIL is fine for loading/saving image files (although if you're using a GUI
toolkit, that
Christian Heimes wrote:
Am 28.11.2012 19:14, schrieb Michael Torrie:
I'm curious. What features do you need that pil doesn't have? Other
than updating pil to fix bugs, support new image types or new versions
of Python, what kind of active development do you think it needs to
have?
I'm investigating Python for image processing (having used Matlab, then Octave
for some years). And I'm spoiled for choice: PIL and its fork pillow,
scipy.ndimage, scikits-image, mahotas, the Python interface to openCV...
However, PIL doesn't seem to be in active development. What I want to
This may be of some interest to you:
http://www.youtube.com/watch?v=Wvvxazwi2IYfeature=plcp
On Wed, Nov 28, 2012 at 1:30 PM, Alasdair McAndrew amc...@gmail.com wrote:
I'm investigating Python for image processing (having used Matlab, then
Octave for some years). And I'm spoiled for choice:
On 11/28/2012 05:30 AM, Alasdair McAndrew wrote:
I'm investigating Python for image processing (having used Matlab,
then Octave for some years). And I'm spoiled for choice: PIL and its
fork pillow, scipy.ndimage, scikits-image, mahotas, the Python
interface to openCV...
However, PIL
Am 28.11.2012 19:14, schrieb Michael Torrie:
I'm curious. What features do you need that pil doesn't have? Other
than updating pil to fix bugs, support new image types or new versions
of Python, what kind of active development do you think it needs to
have? Maybe pil has all the features the
On Wed, 2012-11-28, Christian Heimes wrote:
Am 28.11.2012 19:14, schrieb Michael Torrie:
I'm curious. What features do you need that pil doesn't have? Other
than updating pil to fix bugs, support new image types or new versions
of Python, what kind of active development do you think it needs
I take your point that not being actively developed doesn't necessarily mean
that the software is bad - but in general healthy software is continuously
updated and expanded to meet the needs of its users, or to take advantage of
new algorithms or hardware.
And in its current form PIL has a
12 matches
Mail list logo
