You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Am I correct that there is currently no way to read (private) IFD Tags like "GpsIFD"? However, the necessary parsing method is already implemented and even the offset of the tag is available (tiff::decoder::ifd::Value::Ifd(offset)).
By extending read_ifd, I would offer to add the missing function pub fn get_tag_ifd(&mut self, tag: Tag) -> TiffResult<tiff::decoder::ifd::Directory>.
Are there any opinions or criticism regarding that plan?
The text was updated successfully, but these errors were encountered:
Overall I think your plan seems reasonable. I do wonder whether the tags in a GpsIFD have the same meanings as in a normal IFD? There's also a risk that get_tag_ifd would leave the decoder in a weird state, but that shouldn't be too hard to avoid.
What exactly do you mean with "same meaning"? :) As I understand the standard, all tags live in a namespace of their own and are private to the particular type. As such, I am even allowed to use i. e. tag 256 (ImageWidth) with a completely different meaning within this tag.
Am I correct that there is currently no way to read (private) IFD Tags like "GpsIFD"? However, the necessary parsing method is already implemented and even the offset of the tag is available (
tiff::decoder::ifd::Value::Ifd(offset)
).By extending
read_ifd
, I would offer to add the missing functionpub fn get_tag_ifd(&mut self, tag: Tag) -> TiffResult<tiff::decoder::ifd::Directory>
.Are there any opinions or criticism regarding that plan?
The text was updated successfully, but these errors were encountered: