Ticket #82 (closed enhancement: fixed)
Opened 2007-03-22T13:05:52-05:00
Last modified 2009-03-11T16:52:39-05:00
Better support for writing OME-TIFF, including proposed modifications
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | bio-formats | Severity: | major |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Bio-Formats can write OME-TIFF by inserting the proper OME-XML string into the first IFD using TiffWriter.saveImage(String, Image, Hashtable, boolean), but the TiffData element must be manually injected into the string first, which is inelegant. It would be better to have some API dedicated to OME-TIFF specifically that takes care of TiffData element(s), prepends a reasonable warning comment as per the OME-TIFF proposed modifications (see ticket #80), and other conveniences.
Change History
comment:1 Changed 2007-07-09T10:18:38-05:00 by curtis
comment:3 Changed 2008-03-19T13:55:16-05:00 by curtis
- Severity set to fatal
- Milestone set to bio-formats-m1
comment:5 Changed 2009-03-11T16:45:15-05:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
OMETiffWriter has existed since r3013, and as of r4748/r4749 populates TiffData using the IMetadata API.
comment:6 Changed 2009-03-11T16:52:39-05:00 by curtis
- Milestone bio-formats-m1 deleted
Milestone bio-formats-m1 deleted
Now that we have split off OmeTiffReader from TiffReader, it makes sense to also create an OmeTiffWriter to take care of most of the complexity of building the OME-XML string. This is a necessary step along the path to widespread adoption.