Clicky

blkbird
I have just recently started using HoudahGeo. when i geo-code .tiff files (from a canon Eos1ds). The files are no longer raw files and show up as 288x192 pixel tiff images. Even thought the files are 10mb in size. Photoshop, aperture and file info show the same small size.

Any help would be appreciated.
0 0
houdah
Hi!

I don't quite understand your question. Are you saying that after geocoding, other applications start using the image's low resolution preview rather than the full resolution RAW?

Could you email me a sample image?

Best,
Pierre Bernard
Houdah Software s.à r.l.
Houdah Software s. à r. l.
https://www.houdah.com

HoudahGeo: One-stop photo geocoding
HoudahSpot: Advanced file search utility
Tembo: Easy and effective file search
0 0
houdah
Hi!

BTW, how come your Canon shoots TIFF. I would expect it to shoot CR2.

Best,
Pierre Bernard
Houdah Software s.à r.l.
Houdah Software s. à r. l.
https://www.houdah.com

HoudahGeo: One-stop photo geocoding
HoudahSpot: Advanced file search utility
Tembo: Easy and effective file search
0 0
blkbird
Hi Pierre,

Canon in their early wisdom, made the raw files for the Eos 1 and 1Ds with the .tiff designation......smart thinking ? Then changed to CR2 etc.

After some research I found the following information from here http://photo.net/digital-darkroom-forum/00IluF

"The TIFs from a 1D and 1Ds mk1 (don't know about the mk2s) are valid TIF files and can be opened by most applications that can handles TIFs. But those apps will only see the small preview image, 288 x 192. The RAW data is embedded in the TIF file as well.

The problem with this is you can open the 'RAW' TIF in an image editor, and save it and wipe out the RAW data."

This is the problem I have, once I write the geo information to my files they are no longer raw files. If I try to open the file in Aperture of Photoshop after I have geo coded provides me with a small preview image, 288 x 192 only.

I can send you a .tiff to play with if you like.

Cheers

Greg




0 0
houdah
Hi!

That's quite an odd thing Canon did there.

I guess the best I can suggest you is to convert your images to DNG before geocoding. The catch here being that current versions of Adobe's DNG converter seem to have a bug where they write the wrong timestamp to the DNG. That again causes problems during geocoding. I have posted a workaround to this forum.

Best,
Pierre Bernard
Houdah Software s.à r.l.
Houdah Software s. à r. l.
https://www.houdah.com

HoudahGeo: One-stop photo geocoding
HoudahSpot: Advanced file search utility
Tembo: Easy and effective file search
0 0