Sunip Mukherjee

The encoding/decoding methods are not ubiquitous and require further setup of the encoders and decoders. Serialization and deserialization are not meant for transporting image data across different devices and architectures,...

Using PNG/TIFF is fine as long as the data can be transferred without loss (including channel information etc). However, in my understanding, serialization-deserialization is opaque (correct me if I am...

I see how we can benefit by picking a standard format. As long as PNG (or some other, standard format) can accept all the variants of `DynamicImage` and transfer them...

Will take a crack at it.

Adding 32F support was straightforward, but tiff encoder does not support gray images with alpha channel.

PNG for integer images, TIFF for floating point, then.

I can stand behind separating the image and the metadata, and instead providing the information to the encoders/decoders optionally. As for what is contained, we can probably take inspiration from...

That’s fair, glad to know you are interested. I will break this up into three and submit tomorrow: 1. The “metadata”. 2. Serialization-deserialization. 3. FITS IO.

Through our discussion, I see how metadata is challenging. Storing FITS images also appear to be outside the scope of the `image` crate, because of the niche use case, and...

I think my wrapper for zyre kinda takes care of this problem, see if it suites your use case. https://github.com/sunipkm/peernet.git I have also built a python wrapper for it, in...