I was really puzzled… and in fact, I’m still puzzled, but at least it works now.<\/p>\n
Update<\/strong>: I’m a bit less puzzled now. I wasn’t using the correct version of EXIF.py (see comments). This post has been updated to correct any information. I also updated the I’m now<\/em> using EXIF.py<\/a> for loading EXIF information from photos for my little project, PhotoFile<\/a>. Today, I wanted the image orientation information. Looking in the source of EXIF.py, you’ll find:<\/p>\n So, I tried:<\/p>\n To correct the above, I’m a little lazy with composition, so it’s easier to just post some output from a python session:<\/p>\n There is indeed no “Orientation” tag but there is an “Image Orientation” tag. The string “Image Orientation” appears nowhere in the source, and I couldn’t find any documentation on it. It looks like the tag keys are set by reading them from the EXIF information within the file<\/span> appending the key to the classification (as pointed out by Shirley – see comments), but even the EXIF spec<\/a> lists the tag as “Orientation”. If anybody knows why this is the case<\/span> wants to clarify further, please post in the comments.<\/p>\n So if you’re using EXIF.py<\/a> and want access to the image’s orientation<\/em>, use “Image Orientation” for the key<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" I was really puzzled… and in fact, I’m still puzzled, but at least it works now. Update: I’m a bit less puzzled now. I wasn’t using the correct version of EXIF.py (see comments). This post has been updated to correct any information. I also updated the CODE style because posting python code when whitespace is… Continue reading EXIF.py and Image Orientation<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[3,11],"tags":[48,33,49,47,46],"class_list":["post-185","post","type-post","status-publish","format-standard","hentry","category-geek","category-projects","tag-code","tag-development","tag-exif","tag-photofile","tag-python","entry"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4jEMb-2Z","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/posts\/185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/comments?post=185"}],"version-history":[{"count":0,"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/posts\/185\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/media?parent=185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/categories?post=185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.stevenbrown.ca\/blog\/wp-json\/wp\/v2\/tags?post=185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}CODE<\/code> style because posting python code when whitespace is ignored is a little confusing. ^.^<\/p>\n
\nEXIF_TAGS={
\n\t...
\n\t0x0112: ('Orientation',
\n\t\t{1: 'Horizontal (normal)',
\n\t\t 2: 'Mirrored horizontal',
\n\t\t 3: 'Rotated 180',
\n\t\t 4: 'Mirrored vertical',
\n\t\t 5: 'Mirrored horizontal then rotated 90 CCW',
\n\t\t 6: 'Rotated 90 CW',
\n\t\t 7: 'Mirrored horizontal then rotated 90 CW',
\n\t\t 8: 'Rotated 90 CCW'}),
\n\t...
\n\t0x9003: ('DateTimeOriginal', ),
\n\t...
\n\t}
\n<\/code><\/p>\n
\nimage = open(\"photo.jpg\", \"rb\")
\ntags = EXIF.process_file(image)
\n<\/code><\/p>\ntags[\"DateTimeOriginal\"]<\/code> works fine. But using tags[\"Orientation\"]<\/code> does not work. So finally (it took an unfortunate amount of time to do this), I tried:<\/p>\n
\nfor tag in tags.keys():
\n\tif \"orientation\" in str(tag).lower(): print tag
\n<\/code>\n<\/div>\n
\n>$ python
\n>>> import EXIF
\n>>> p = open(\"photo.jpg\", \"rb\")
\n>>> tags = EXIF.process_file(p)
\n>>> for key in tags.keys():
\n...\tif \"orientation\" in str(key).lower() or \\
\n...\t\"datetime\" in str(key).lower(): print key, \": \", tags[key]
\n...
\nEXIF DateTimeOriginal : 2006:03:19 14:22:40
\nImage DateTime : 2006:03:19 14:22:40
\nEXIF DateTimeDigitized : 2006:03:19 14:22:40
\nImage Orientation : Rotated 90 CCW
\n<\/code><\/p>\nConclusion<\/h3>\n