Ticket #344 (closed enhancement: fixed)
Opened 2009-01-07T11:39:15-06:00
Last modified 2011-02-02T04:45:00-06:00
More robust support for 1, 2 and 4 bit images
| Reported by: | melissa | Owned by: | melissa |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | bio-formats | Severity: | minor |
| Keywords: | Cc: | FCORNELI@… | |
| Blocked By: | Blocking: |
Description
1, 2 and 4 bit images are currently supported, but not in the most flexible way. Instead of storing these images in their original bit depth, we automatically convert them to 8 bit data and throw away the original bit depth. We should do the following:
- use the type BufferedImage.TYPE_BYTE_BINARY when constructing BufferedImages
- add a new flag to the API to toggle how openBytes handles < 8 bit data - developers can choose whether to get original data (e.g. 1 byte represents 8 pixels), or expanded data (i.e. 1 byte represents 1 pixel)
- potentially add new pixel types to the OME data model (uint1, uint2, uint4, etc.)
- update the TIFF writer to export 1, 2 and 4 bit data