mirror of https://github.com/dsoprea/go-exif.git
9068786204
- These are absolute representations of where an IFD is positioned with respect to the other IFDs. There is a more-specific, "fully-qualified" form of the IFD-path that allows you to express indices in order to refer to specific siblings. - Eliminates issues with IFDs at different levels potentially having the same name (if that's what is required with a certain dataset/ datasource). - There is a specific IFD registry that controls the heirarchy of IFDs that we recognize and the tags associated with the child IFDs. This allows custom hierarchies replacing even the TIFF specification for which are expected in an image (so we can read other types of images or any potential IFD hierarchy, even non-image ones). - IFD and IB instances embed the IFD-path and FQ IFD-path that they were found or built for. |
||
|---|---|---|
| .. | ||
| raw_tags | ||
| DC-008-2012_E.pdf | ||
| DC-008-Translation-2016-E.pdf | ||
| NDM_8901.jpg | ||
| NDM_8901.jpg.exif | ||
| NDM_8901.jpg.thumbnail | ||
| PNG-GROUP-DRAFT PNG proposed eXIf chunk, draft 2017-06-15.pdf | ||
| exif_read.json | ||
| gps.jpg | ||
| tags.yaml | ||
