GPS in DNG

My panasonic .rw2 files have GPS data in sidecar XMP files. When converting the .rw2 files to DNG, the GPS data is not transferred. Is there a mehtod of achieving this?

Thanks, John, that would do the trick but also not allow you to use any metadata presets, such as copyright info.
Another forum I belong to (ephotozine.com, an excellent one in London you might want to check into) steered me to a better answer from here in the Adobe forums - https://forums.adobe.com/thread/1414500
Simply uncheck the boxes in "Edit Presets" for info you don't want to overwrite or clear, but check the ones you do, such as copyright and contact info.
By unchecking the "Camera Info" boxes, I was able to solve my problem, but still use the metadata presets, which is a real time-saver.

Similar Messages

How do I update Date Time Digitized to match an updated Capture Time for a DNG file?

I am updating capture time based on GPS Time (a bit OCD, I know) but when I change Capture Time the Date Time Digitized value does not change. This in in LR 4.3 and is not affected by whether on not the Catalog is set to 'Write date or time changes into proprietary raw files'. Maybe this is a problem for DNG files only.

GreSep wrote: I saw another LR discussion that said that with LR 4.3 updating Capture Time would also update Date Time Digitized but it does not do so for me on my DNGs (and as of last month ALL my images were converted to DNGs).
One or two intermediate versions of LR 3 (perhaps Lr 3.6) set DateTimeDigitized when you gave the Metadata > Edit Capture Time command. But for people managing scans in which the capture time of the original image was different than the scan time, this behavior overwrote their scan times, so Adobe backed out of that change. Before and since those versions, the Metadata > Edit Capture Time command just changes the EXIF:DateTimeOriginal and related fields in XMP and IPTC.

Can't open .DNG files in Preview and others

I am using Adobe DNG converter OR Lightroom to convert .RW2 from a Panasonic Lumix 3 to .DNG
This works:
1. Working with files in LR
2. Use PanoMaker to create panoramas
3. Create HDR with Photomagix
This does not work
4. Open files with MAC OS X 10.4.11 Preview (Vorscha) even though thumbnails look ok.
It says (in German) that it can not open the file
5. View files in Houdahgeo - Adding GPS info works
5. Use Photomagico to creat slide shows - only see thumbnails at the bottom
I also played with the settings in Adobe DNG Converter and LR (Raw 2.4, 4.1, 4.6, 5.4, User...Linear...Not compresse) but it did not help.
I searched multiple forums, found the problem twice mentioned on the side but never resolved. One hinted that its a problem since 10.4.11
Message was edited by: schillab

Hi,
(1) I'd think that if Adobe makes a XYZ to DNG converter for MAC OS X the goal would would that the following can open such a DNG file
        (a) All Adobe Apps ..... it works ....... mission accomplished
         (b) The native DNG viewer in OS X which is "Preview" .... it does not work!!!
         Note: the above works if XYZ is Canons RAW. If it is coming from a Panasonic LX3 one is out of luck
(2) I just tried the above with LR 2.6RC and DNG Converter 5.6. Nothing has changed.
Anybody having an idea? work around?
Christian

Can't open .DNG files in Preview

I am using Adobe DNG converter OR Lightroom to convert .RW2 from a Panasonic Lumix 3 to .DNG
_This works:_
1. Working with files in LR
2. Use PanoMaker to create panoramas
3. Create HDR with Photomagix
_This does not work_
4. Open files with MAC OS X 10.4.11 Preview (Vorscha) even though thumbnails look ok.
It says (in German) that it can not open the file
5. View files in Houdahgeo - Adding GPS info works
5. Use Photomagico to creat slide shows - only see thumbnails at the bottom
I also played with the settings in Adobe DNG Converter and LR (Raw 2.4, 4.1, 4.6, 5.4, User...Linear...Not compresse) but it did not help.
I searched multiple forums, found the problem twice mentioned on the side but never resolved. One hinted that its a problem since 10.4.11
Message was edited by: schillab

.... 3 additional additions to my original message.
(a) I am still on Tiger 10.4.11
(b) The conversion if from Canon's CR2 to .DNG in Adobe Raw Converter (ARC) or LightRoom (LR) can be viewed in Preview just fine
(c) It almost looks like ARC or LR convert in way which is good encough for LR and a few others (Panomaker, HDR tools etc.) but not for all
Any ideas how to fix?

Add GPS and keep Metadata

I use Lightroom 1.4.1 (WinXP) to import photos from my CF cards and then add GeoTag data later, without losing metadata. My process has a few steps and is as follows:
Note: Assumes photos are in Lightroom and may or may not have metadata. I have only tried this with Nikon raw .NEF files. Not sure how this will work for file formats that Lightroom embeds directly rather than using .xmp
1. In Lightroom select files you are going to GeoTag and in Metadata menu select Save Metadata to files. Since I am working with raw that has a proprietary file format it creates a .xmp sidecar file for each photo.
2. Probably a good idea to exit Lightroom, after it has finished writing Metadata.
3. GeoTag photos ( I use Microsoft Pro Photo Tool w/ Nikon Raw Codec installed to embed GPS in .NEF files, but expect other tools that embed GPS data into photo files will work fine.)
4. Change modify date/time stamp for each .xmp file. Need a utility (like File Renamer Basic, its free) that will change file modified time stamp of the .xmp files to current time. Seems Lightroom will not read file if it has the same date/time as when Lightroom wrote it. Without this step it seems it reads the raw files metadata and clears Lightrooms database of other metadata for that photo.
5. In Lightroom select files you GeoTagged and in Metadata menu select Read Metadata from files. Lightroom sees different date/time for both .raw and .xmp and so reads each back in.
6. Should now have GPS data for each photo along with its Lightroom created Metadata.

The NEF codec might be the only one that works with the Pro Photo Tools. The Canon CR2 codec appears to save the geotag info, but Lightroom won't recognize it when I import (either keeping the CR2 or converting to DNG).
The new Adobe DNG codec for WIC won't even allow the Pro Photo Tools to save the modified metadata. I get a very unspecific error, but can't find any sort of error log to get any additional details.
-Matthew

Faillure writing metadata to some DNG files

I'm having a problem writing metadata to some dng files using Lightroom 2.6.1. When I try to apply a metadata template to a batch of files most of them get changes but a few don't. This only effects DNG files so far JPEG and TIFF seem to be OK. I have tried running the problem files through DNG converter and the new files have the same problem. Lightroom won't write to them.
I can change the metadata of these files from Bridge. The changes then appear properly in Lightroom. Afterwards I can change the metadata again from Lightroom.
I'm working on a MacBook Pro (Late 2008) and running OS 10.6.2.

I created a preset to export to same folder as original, same format as original, and stack with (above) original. I used this on the seven files, and it has solved the problem without losing any metadata.
The jpegs had at some point been processed by Photoshop Elements as they were imported/edited using that application in 2010 but the metadata problem didn't show up until recently when I was making some adjustments in Lightroom. I somehow think this may be related to the GPS tag though I don't have sufficient evidence.
The DNG file was strange in that it was straight the camera with no Lightroom adjustments, although I did add GPS info in the Map module. Anway it is now fixed as well as the jpegs.
With this preset it would be possible quickly to fix a large number of image files. Just create a Smart Collection to display the problem files and run the preset on them all in one go. The only things that I am aware of that you would need to look out for are (1) if they are in a collection other than a smart collection, or have been published to a service like Flickr or to the Hard Disk the link will be broken, and (2) If you like to sort photos by date/time added, they will be out of the sequence (capture time is fine).
When you are satisfied that this has worked OK then you can delete the images from the "Metadata Not Up To Date" smart collection. Select all, go to all photos, they should remain selected and press Delete. You could do a thousand in one go if you have the nerve for it
Hope this helps.
Peter

Canon GP-E2 compass bearing information in LR DNG

I received a Canon GP-E2 yesterday, and used it on my Canon 5D Mark III. It encodes GPS coordinates and compass bearing directly in RAW files.
I shoot in RAW, and import the RAW files into Lightroom 4.1 using the "copy as DNG" option.
After importing my test shots into LR, the GPS coordinate data showed up as expected in the EXIF metadata, as did the altitude. However, I do not see any indication of the compass bearing.
When I use the Canon utility software that came with the GP-E2, it does display compass orientation on its map display, so bearing is obviously being stored in the RAW file.
My guess is that Adobe's DNG specification has no tag or field for bearing yet.
If anyone has any greater knowledge or understanding about this, I'd appreciate learning more.
I'd also like to know if Adobe has plans to update DNG to capture this information.

The GPS image direction and reference are in the EXIF data in the 5DM3 raw files and also in the .dng files I have from my 5DM3/GP-E2 combo. I performed the CR2 to DNG conversion using Lightroom 4.1.
Not all EXIF editors/viewers are updated to show the GPS Img Direction Ref and GPS Img Direction fields.
Phil Harvey's exiftool 8.89 is one that does show the data, if present, when reading .dng files. At this time Lightroom apparently does not.

Is there a way to integrate Adobe DNG Converter into Lightroom 5.7?

I recently purchased an Olympus OM-D E-M5 Mark II. Unfortunately, the new Olympus ORF raw file is not recognized in Lightroom 5.7. I am currently running a separate operation on all of my new raw files - running them through Adobe DNG Converter. This takes time as a separate operation, and I'd like to make the conversion automatic within lightroom. Is this possible?
Thanks!

Buy Downloader Pro.
Downloader Pro - Download, Organize, Rename Images Photos Canon, Fuji, Minolta, Olympus and Pentax Digital Cameras
I have been using this with LR for a long time now.You can incorporate the Adobe DNG converter into the download process. I initially bought Downloader Pro because it has an extremely flexible file renaming facility, but besides renaming files it can integrate GPS information into images from my handheld GPS receiver, hand off the files to the Adobe DNG converter and then place the resulting DNG files into LR's Auto Import folder, making the entire process automatic.

Change in GPS coords in LR 1.4.1???

Has v1.4.1 had a change to the GPS metadata panel? I use RoboGEO to upload geodata from my GPS unit and then tag the images prior to importing into Lightroom. Previously by clicking on the GPS button in the Metadata panel Google Earth has opened up and the location my images(s) was taken from has shown up perfectly.
However, upon return from a shoot yesterday I have tried the same operation and sequence as I have always done but with strange results. The only thing that has changed in my workflow is the upgrade to version 1.4.1 and so can't help but feel that my problem lies somewhere in that direction.
For instance, checking on my GPS unit for a particular waypoint that I have saved shows this to be 48°33'1150" N - 8°59'1442" E. When transfering from the GPS unit to RobOGEO exactly the same data is shown to be stamped to the images EXIF data. I have even entered these coordinates manually with the same results.
Back in Lightroom however, the coordinate data is different and of course when opened in Google Earth a completely different location is shown. The same coordinates as stated above show as 48°19'54" N - 8°35'29" E in the Lightroom panel.
Has anyone any idea whatsoever as to why this should be as this is now becoming very frustrating? Just to repeat, I never had this problem until upgrading to v1.4.1 and that is the only thing that has changed in my system or workflow.

Eric
Yes sure. On my Garmin Map60CSx I use the 'Mark' button to set the Waypoint from where I have taken the shot. I then change the name that Garmin automatically sets for it to the image number - so for example if the image number is IMG_001.CR2 then I name the Waypoint number to 001. This makes it easier to tie up Waypoint to image later in RoboGEO as both will be unique. Before saving the Waypoint I use the Avg (Average) button which calibrates or fine tunes the Waypoint any number of times. I usually let it run to around 50 times noting how the +/- value changes. Once it has steadied I then save the Waypoint. Obviously the final accuracy of the saved Waypoint will depend upon the type of terrain (clear sky or overhead trees etc )one is in but generally speaking I have been very well satisfied with the results.
CR Henderson
The time the Waypoint was saved plays no part in the issue which is why I prefer this method over and above the track method.
From the File menu in RoboGEO (or using Stage 1 in the left hand panel) I import the CR2 images (or sometimes DNG's if I've converted them first). When the images are imported they will be listed in the main window from which I highlight the first image - say 001 using the example above. Moving to Stage 2 in the left hand panel and with the GPS connected to the computer I click on 'from GPS waypoints'. This opens another window in which all the saved Wapoints on my GPS are listed. I then click on Waypoint 001 to match the image 001 which then lists the coordinates for that Waypoint in the main window alongside the image. In Stage 3 I then click on 'write location data to EXIF headers' which then stamps the coords into the image. Job done and pretty simple and as said previously my preferred method because setting and averaging a Waypoint I find to be far more accurate which in your own experience can be 100 feet or more out. Time is not an issue here because one is quite simply matching image to Waypoint. The time the Waypoint is set doesn't enter into the equation only that one doesn't move away from the original place of course. This differs to your chosen method in so much as there are many areas in which time DOES play a part and which is prone to several areas of innacuracy. For example, if your time in your camera and GPS are not PRECISELY matched then this will obviously induce error. RoboGEO is matching the 'time' the image was taken (from the images exif data) to the nearest track point set at that time. If your camera and GPS times differ by 1 minute .........well one can cover a lot of ground in that time. :-)

DNG and MESZ timestamp / sony A100 RAW conversion

Hello,
i have a question regarding the timestamp within the EXIF metadata after the RAW to DNG conversion for my A100 pictures. Today I have seen that the timestamp betwen the RAW original file and the converted DNG file differs about 3 hours. I can't explain me this difference by myself. Has someone here an idea for this difference? I use the Mac Version of the actual free DNG converter. My timezone is MESZ/CEST what also means UTC+2 at the moment if I'm right. So 2 hours difference I could imagine because of such a time zone missmatch, but not 3 hours. But if i look at the RAW files the timestamp addition also shows MESZ like in the DNG after conversion. The main reason why I want to use DNG format is the linkage with my GPS logger data. But if the timestamps will convert wrong, this would be a no go for me.
Thanks for your help.
Greetings,
Tschubi

I think what you are seeing is a longstanding mis-match between how Exif and XMP record date-time values, and--possibly--a failure on the part of some of your software to understand how to use date-times read from XMP for the Exif date-time properties. When reading an Exif date-time from XMP, the UTC offset should always be ignored when interpeting the date-time--it has no meaning.
Three date-time metadata properties are involved in this issue, in XMP they are stored as the following properties:
exif:DateTimeDigitized
exif:DateTimeOrigional
xmp:ModifyDate
When Adobe software reads Exif metadata from files, it maps the values in the Exif tag(s) to XMP properties. The XMP is stored inside the file when the software saves or updates a file (or sidecar .xmp file for RAW files).
For exmaple, the exif:DateTimeDigitized the value is taken from two Exif tags, 0x9003 ("DateTimeDigized") and 0x9291 ("SubSecTimeDigizied"). See Part 2 of the XMP Specification for more details about how Exif is mapped to XMP.
The Exif specification defines no way to record a time zone or UTC offset for its date-time values. If you are trying to figure out what time the picture was taken reading Exif, it's impossible to know what time zone is correct. If cameras are recording the time zone, they are storing it in propritary metadata in the file, and not in a standard Exif tag.
Unfortunetly until recently the XMP Specification defined a date-time string format that requires a UTC offset. That's the mismatch. So, what's the software do when it's supposed to write a UTC offset, but doesn't have one to go with the time? Traditionally Adobe software uses whatever time zone your computer's clock has at the time the XMP property is created (that is, when the Exif is read).
So, if your camera's clock was set to record 2009:08:28 11:26:07 in the Exif, and you convert your raw file to a DNG with a computer in Europe, you're probably going to get something like 2009-08-28T11:26:07+02:00 in the XMP. But if I convert the same RAW file to a DNG here in Seattle, I'm going to get 2009-08-28T11:26:07-07:00.
Of course the right thing to do would be to just write 2009-08-28T11:26:07 in the XMP, leaving out the time zone designator (TZD). Expect that in the future. The XMP Specification now says that the TZD is optional and that "software should not assume anything about the missing time zone," but even the most recent release of the DNG Converter (5.5 as I write this) has not yet caught up with this update to the XMP Specification, and it still writes the bogus TZD. Also, any XMP written by older Adobe software will have the TZDs.
What Adobe software like Bridge and Lightroom have done tradtionally is to ignore the TZD in the XMP when using these dates. You'll notice that browsing DNGs with the dates 2009-08-28T11:26:07+02:00 and 2009-08-28T11:26:07-07:00, and running Bridge anywhere in the world (that is regardless of the the clock's Time Zone setting on your computer), the metadata panel will still show you that you took the picture at 11:26 am on August 28, 2009. If other software is trying to shift dates to local times based on the UTC offsets recorded in XMP for these dates, that's a bug.
Note that unlike other date-time values in Exif, the Exif specification says that the GPSTimeStamp is UTC, so this problem does not affect GPS metadata.
I mentioned the XMP specification a few times, you can download it here:
http://www.adobe.com/devnet/xmp/
-David

Cannot open DNG files in CS3

I transferred files from my camera a Panasonic G3 to Lightroom 4 converting them to DNGs and then made a quick selection of those I wanted to process further in CS3. When I try to open any DNG in CS3 it tells me it cannot because " it is not the right kind of document" I have no trouble opening JPGs in the same collection. How can I get the DNGs to open?

Check your metadata stuff. You are probably retaining GPS data or otehr stuff that back then didn't exist. also verify, that your DNGs use the right DNG version.
Mylenium

EXIF Data Lost for Edited DNG Files

I'm having an issue where my photo's EXIF data is lost when I export the picture from iPhoto. This only happens after I edit a RAW (DNG) file and export it. If I export the RAW file before editing the EXIF data is fine. Is this a bug?
System Info:
iPhoto v.7.1.3
RAW format type is Adobe DNG.
Camera is Pentax K10D
Mac OS X v.10.5.2.

I've been having the same trouble for a few months now. All EXIF is lost, including GPS and focal info. It only occurs when you edit a RAW/DNG file and have the "save edits as 16-bit tiffs" selected in the preferences. Please, Apple, help! This is a significant issue when exporting photos! That info is essential.
thanks,
Brett

Problem with JPEG files from Leica M and GPS data

It seems there's a serious bug in Camera Raw 8, hosted in Bridge CS6 on an MS Windows machine, with regard to GPS metadata.
When using a Leica M (Typ 240) with a multi-function handgrip then both the DNG files (DNG is Leica's native raw format) and the JPEG files out of the camera will include GPS position data in the respective EXIF metadata sections. However, Bridge refuses to display the JPEG files' GPS data (while there's no problem with the GPS data in the DNG files). Worse yet—when loading a JPEG file in Camera Raw for some parametric adjustments and saving the file then the GPS data will be entirely gone! (Again, no problems with the DNG files' GPS data.)
I suppose that Camera Raw 8 hosted in Bridge CC as well as Lightroom 5 are suffering from the same issue.

Nobody? Absolutely nobody?? Zalman? Eric? Anyone?
If you need more input from me then please talk to me.

GPS Metadata missing in Bridge

I have a problem with seeing GPS metadata in Bridge CS2. I use a Gisteq datalogger to add GPS data to my DNG files and it writes the data to the associated XMP file. I can see it there if I open the XMP in Notepad. If I view the file in Bridge, the GPS fields are blank. I have set preferences to display all metadata fields even if blank. Is this a bug?

I just solved the problem myself. I am using Gisteq Phototracker Pro to add GPS data. It works OK when a add the GPS data to a JPG. I can view the GPS data in Bridge. When I use a DNG file, I converted directly to a DNG in Bridge from the RAW file but did not do anything else with it. I then used Phototracker which created the XMP file with the GPS data in it. There was no XMP file until then. I could see the GPS data in the XMP in Notepad but Bridge did not see it.
I picked up the DNG file in Bridge and changed some settings in Camera Raw and resaved the DNG. It could then see the GPS data in Bridge. Bridge did not know the XMP had been associated with the DNG after Phototracker had created it until I did something with it in Bridge.

Mac: Copy/paste GPS Exif data in LR 2? Or workaround?

Hello,
does someone here know a workflow to transfer GPS Exif metadata from a tagged JPEG to DNG/Raw pictures in LR 2 on Mac?
I have a Nokia 6220 classic mobile to shoot geotagged pictures. The pictures I take with my DSLR in the same location should get the GPS data.
G. Friedls Geotagging-plug doesn´t utilize the Exif metadata fields in the metadata panel (as far as I understand)...

Hello,
does someone here know a workflow to transfer GPS Exif metadata from a tagged JPEG to DNG/Raw pictures in LR 2 on Mac?
I have a Nokia 6220 classic mobile to shoot geotagged pictures. The pictures I take with my DSLR in the same location should get the GPS data.
G. Friedls Geotagging-plug doesn´t utilize the Exif metadata fields in the metadata panel (as far as I understand)...

GPS in DNG

Similar Messages

Maybe you are looking for