Add support for data type 13 (IFD offset) #197
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some cameras (Sequoia Parrot in my case) use the non-standard tag type
13to indicate an offset to an IFD, as recommended on ExifTools homepage here: https://owl.phy.queensu.ca/~phil/exiftool/standards.html (see section "TIFF 6.0" / "A simple solution").For exif-js' purpose, the only change needed to handle this is simply to treat data type 13 the same as data type 4. With this change, I can read GPS information from the Sequoia Parrot camera (without the change the GPS IFD is ignored by exif-js). ExifTool does the same, so this should be safe to do.