ImageDataGenerator would belong here?

[cocoa-xu]

ImageDataGenerator would belong here?

[cocoa-xu]

Yeah, I think a library similar to the imutils could be the go.

IMHO, although these image processing/manipulating operations/functions could belong here, it would be easier to maintain and more flexible if it was a separate project.

[cocoa-xu]

I feel like the ImageDataGenerator could perhaps be a separate project and use Evision as a dependency (maybe an optional one). Potentially, it could also use other image processing backends (so that users can select which one to do the actual job) in this way.

For example, if a user is already using Evision in their project, then they can use Evision as the backend. If they're not using Evision and there is some other tiny image processing library that could handle all needed operations, then they can choose to use the lightweight one.

WDYT?

[vans163]

Yea, separate project works. Also what about the transformations such as shear, zoom, shift, brightness would those belong separate or here?

EDIT: Note this is generally accomplished by imutils in python which is a utility library for opencv.

[kipcole9]

It's possible you might find Image based upon vix that is Elixir bindings on libvips for the functions you referenced. While Image might not have all the convenience functions you're after, libvips certainly does and they are all exposed in Vix/Image.

I've just added experimental support for eVision interoperability. This is basically zero-copy data exchange between eVision/Nx/Image(Vix).

[cocoa-xu]

I'm closing this issue as I believe it would be better to implement this (and other related features) in another library.