Ticket #82 (closed enhancement: fixed)

Opened 13 years ago

Last modified 11 years ago

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:


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 13 years ago by curtis

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.

comment:2 Changed 12 years ago by curtis

  • Priority changed from major to critical

comment:3 Changed 12 years ago by curtis

  • Severity set to fatal
  • Milestone set to bio-formats-m1

comment:4 Changed 12 years ago by curtis

  • Severity changed from fatal to major

comment:5 Changed 11 years ago 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 11 years ago by curtis

  • Milestone bio-formats-m1 deleted

Milestone bio-formats-m1 deleted

Note: See TracTickets for help on using tickets.