Hi,

if you run this script, and the currently selected image contains GPS coordinates, IMatch will open a web browser and navigate to the coordinates of the image in Google maps.

There are other scripts which allow you to input GPS coordinates into an image, and also scripts which display the image in Google Earth (if you have it installed).

There's not much more that I can say to add to my lengthy post in the quoted thread. My script doesn't copy the XMP because there's no scripting method to do so. The underlying code exists in iMatch, because copy & paste attributes from the menus allows it, but this hasn't been included in the scripting engine yet.

I think that what I would do in this situation is initially place the JPG in the same folder as the RAW file. iMatch would then assign it the same XMP sidecar file as the RAW. I would then use iMatch to move the JPG to another folder, which would copy the XMP sidecar, including the GPS information.

What I do now is use the GeoTagger script (and ExifTool) to insert the GPS info in the RAW file, and then use my synchronisation script. Not everyone will be comfortable with this approach, but it works for me.

F_P

Sorry about that... the link refreshed me on the issue thoroughly, and I don't deal with XMP sidecars, so I haven't encountered that limitation with Ferdinand's script. I can understand your fears with scripting.

The only other thing I could think of would be to write a very simple script (or two)...

1. One script or routine to open an xmp file and read the GeoTag information. xmp files are essentially a text file with the benefit of xml tags that will make finding the exact information you are looking for rather easy. I would just read those values to the clipboard or perhaps to an image property.

2. Another script or routine to potentially save the information on the clipboard to the GeoTag information for the target JPG file. In this case, you'd probably have to write to the GeoTag EXIF information.

Unfortunately, I'm not a scripter either, so I'm not sure how easy this would be, especially if you need it to go through a batch of files.

I would like to know where and when you loose the GPS metadata. When I download the pictures with DLPro, like you do, I also immediately convert them to DNG with the plugin for DLPro. So after import, I have the original RAWs, the in-camera JPEGs and the converted DNGs. I put the JPEGs as a small-size last resort backup on an old external disk and delete the original RAWs. I use the DNGs for all the rest. Now, if I look at the RAWs, JPEGs and DNGs as well as any JPEGs made from the DNGs, the GPS data is allways there ... I don't need to copy it.
SO the question really is: How and where do YOU loose it? If you can simply avoid that, your problem is solved.

If you're working with a recent copy of DLPro, then AFAIK it is sticking the GPS information in an XMP sidecar. It will be lost in a workflow that doesn't keep the sidecar with the converted JPG. I guess Adobe applications should keep them together. Bibble 4 doesn't but Bibble 5 should. Some RAW converters will and some won't.

If anyone is thinking of modifying a script to transfer GPS from an XMP sidecar for a RAW file to EXIF for a JPG, I suggest that the Geotagger would be the script to modify, rather than my synchronisation script. The Geotagger is all set up to do this, and only needs to be modified to read the GPS from the XMP text file instead of the script's dialog box.

F_P

I just can't understand all the hassle. After importing my NEF to the disk I run GeoSetter which writes the geotags to the NEF.

All jpgs derived whith any decent program will inherit the geotags in their Exif, a place where most geolocalisation programs will look for them and find them. It never failed.

Normunds' Bibble Integrator script offers the possibility to have the geotags copied from raw to jpg (it relies on exiftool) which works but is very slow (Bibble is not needed here, it is in the synchronizing part of his script).

Francis

Exactly!
And I don't have any sidecar files for my JPEGs!?! The metadata is in the JPEGs (and in the DNGs - or NEFs in your case).
But I just tested with RawTherapee and it effectively drops the GPS info when it converts my MRW to JPEG. But when it converts the DNG to JPEG, the GPS info is kept ...
Fortunately, I use ACR/Photoshop which don't drop anything.

Thank you Ferdinand, emalvick, Lensview and Cytochrome for responding!



After import with DLPro I have a raw file and a corresponding xmp sidecar, like 12345.cr2 and 12345.xmp.
I don't use DNG nor in-camera JPG, raw is all there is.
My raw converter of choice is DxO Optics Professional (DOP), which does not take into account the xmp sidecar. Hence the output of DOP lacks GPS info. I filed an enhancement request at DxO, but I don't know if and when that will be honored.
Like Ferdinand said, some raw converters do add GPS info into the output JPG EXIF fields, some don't. I have one converter installed on my PC that does add the xmp sidecar GPS data into the JPG output EXIF fields, but that is not my preferred converter. Using that converter would eliminate this problem, but introduce some others.

The suggestion made by Ferdinand to write the GPS info in the raw file is something I am considering. It all depends if a raw file which has been modified this way can be processed by DOP. I will have to run some tests here.

Anyway, I will see what the geotagger script can do in this area first.

Thanks for the suggestions!

hi, Mario,

i DOWNLOADED exiftool. where do I need to place it so it can be used by IMatch script for GPS? and should I rename the downloadable to exiftool rather than the orig filename of exiftool(-k).exe? thanks.

dick louderman

An issue I think some are forgetting is that very few RAW formats accept metadata XMP embedding into the file, which I believe includes the Geotags.

This is what led me to a DNG based workflow where I do embed the Geotag to the EXIF and then XMP (through the XMP update) where these are all embedded. I lack patience and switched from my PEF format mostly because I didn't want to have to deal with the issue you are facing and didn't bother thinking about how to deal with it.

A couple programs I use don't always pick up the metadata when processing the RAW to a TIFF or JPG (e.g. Rawtherapee), so that is where I usually take advantage of Ferdinand's script since I am sync'ing more than just the Geotag (categories, IPTC, etc). I do use Geotagger quite often for my photos, and that is one of the scripts I was thinking about when I suggested reading from the sidecars.