so more architecture. we're facing data design question whether should add used table our image class (which contains actual raw data) or not.
arguments may palettes part of usual image classes in libraries. see example bitmapsource.
arguments against may lut modification scale on image representation (eg. viewer). going viewer property. not necessarily.
so opinion on it?
if data contained in image makes sense when associated lut, include lut in image.
if lut used presentation purposes of sort of data make sense when not associated lut, put lut outside of image class.
for instance:
- for gif image put lut in class, because raw data doesn't make sense if not associated correct colors.
- for image containing b/w data, or each pixel represents "people per square mile" or other data can stand on own, put lut outside
if need lut both converting raw data meaningful data (e.g. gif palette rgb) , presentation (e.g. highlight structures in bw image) lut should have own class, image should link lut needed derive meaningful data raw one.
for instance, dicom standard (medical imaging) allows both presentation lut , "transformation" (invented term, don't remember correct one) lut: can have plenty of presentation luts highlight different part of image, 1 transformation lut used derive meaningful data raw data meaning known producer of medical device. image has 1 link transformation lut, not aware of presentation ones.
Comments
Post a Comment