Is Canon lens focusing distance in EXIF data?

[David R. Gurtcheff]

I use DXO Optics pro to convert RAW and correct lens faults. DXO needs to know focusing distance to make it's corrections. I've been "guessing" the distance. Is this info available in the camera data for each exposure? I can't find it anywhere!

Thanks in advance
Dave

[francois]

Canon doesn't seem to embed distance in EXIF. I don't know if it is present but hidden in "private" tags or simply not added to the EXIF header. In addition, not all Canon lenses provide distance info to the camera, so for these ones, guesswork is the name of the game. A list is available on Canon's website.

[David R. Gurtcheff]

Canon doesn't seem to embed distance in EXIF. I don't know if it is present but hidden in "private" tags or simply not added to the EXIF header. In addition, not all Canon lenses provide distance info to the camera, so for these ones, guesswork is the name of the game. A list is available on Canon's website.
[a href=\"index.php?act=findpost&pid=63577\"][{POST_SNAPBACK}][/a]

Thanks Francois.......
Dave

[saatchlwook]

For all of my Canon lenses, the Canon 10D has exif data of Subject Distance, but I only recall it's being available when I right click a jpeg and go to Properties/Summary/Advanced (in WinXP).  Of course this means that if I need to know the SD for proper RAW conversion, I first have to make a jpeg, look up the data, then do a second conversion...  
I don't know if it'll make a difference, but I use BreezeBrowser for RAW conversion--different RAW converters may create different exif sets visible to Properties

ps: Don't know if it's relevant to your software, but the SD data from the 10D is always way off the actual physical distance at which the lens was focused..

[francois]

From what I recently read on the web, distance is present in EXIF data when the used lens has distance reporting capabilities. A list of those lenses has been published by Chuck Westfall back when ETTL-2 was announced. However, a dissection of decoder rings (here) seems to indicate that a range of distances is reported rahter than a exact value. This might explain why you find you distances somewhat weird.

Please, note that I'm not a specialist in decoder rings