GPS Exif metadata bug
Hello,
When I try to upload a Geotagged JPEG generated by Lightroom, GEOdata is lost (the same happens with picasa). The problem is not flickr but lightroom! You can check it following these steps:
1- Geotag a RAW file (I did with geosetter)
2- Import & convert to DNG (lightroom) and check GPS data is showed in metadata.
3- Export to JPEG and manually upload it to flickr.
Doing this way, GEOdata won't show up in flickr. But following these steps:
1- Import & convert to DNG.
2- Export to JPEG.
3- Geotag the JPEG file (I did with geosetter)
4- Manually upload it to flickr
Works great!
In this link www.flickr.com/photos/dpecos/3054904739/ are show both GPS metada: the top one is the one that works and the bottom the one exported directly from lightroom. As you can see there are less GPS Exif headers.
Thank you!
I get more locality information (city, state, etc) if I geotag a JPG compared to a RAW but both have coordinate information embedded in them and show up on my map. I use LR's Flickr upload plugin for the RAWs so maybe that's a difference. I always geotag both the CR2 and the XMP and I never convert to DNG, so maybe that's the difference.
Can you confirm that when you geotag before importing into LR (the situation that doesn't seem to work for you) that clicking on the GPS -> in the metadata section shows the correct location on the map from w/in LR?
Besides the extra tags on the top EXIF dump that really don't seem important, I see a couple differences between the information:
1) The longitude on the top/working EXIF is relative to W while the longitude on the bottom/non-working EXIF is relative to E. And they appear to be coordinates to totally different parts of the world. Can you confirm where each is, approximately, at least country and nearest city?
2) The longitude on the top/working EXIF seems to have all three parts in D M S format, while the bottom/non-working EXIF seems to have D M.MMM with 0/0 (infinity) for the third, presumably unused portion of the coordinate.
Not sure if either thing contributes to the problem.
Similar Messages
-
Photoshop Bug? GPS exif metadata stripped out
We recently discovered that ANY changes made in Photoshop CS4 stripped out our GPS exif metadata. We also tried it in CS3 - same thing! And by changes, this includes anything - changing IPTC, adjusting levels, etc. It even happened when just opening, re- saving and closing the file in Photoshop.
FYI: We tested it with images exported from both Adobe Camera RAW (Canon files) and Phocus(Hasselblad), and the problem occurred with both. We've also tried it with files from different cameras, which used different GPS brands altogether, therefore we can rule out: the GPS units, camera (Canon 1Ds Mark II, Hasselblad H3D-39), and software used to convert RAWS (Phocus, Adobe Camera RAW, Lightroom). We also tried different computers to make sure no preferences were corrupt on an individual machine, to rule that out.
To make things even more complicated, we just discovered that even though we can no longer see the GPS info in Photoshop CS4, Adobe Bridge DOES see the GPS info! But - none of our other softwares which normally recognize GPS can see the info (iView, Cumulus).
Very, very frustrating.......HELP!
Mac OS 10.5.6, PowerMac 2 x 2.66 GHz Dual-Core Intel Xenon, Photoshop CS4, Files exported to Prophoto RGB 16-bit TIFF) using both Lightroom and PhocusAddendum: Does anyone know how to add EXIF back into a file?
I assume this would be difficult, as EXIF is hard to remove, much less put back.
Many of these files have already been worked on extensively, and re-importing and re-working is not a good option.
We have already tried the following (did NOT work):
1) Exporting the XMP from the file BEFORE any changes are made (with GPS info still intact), and importing XMP to finished file (tried all 3 option settings)
2) Copy and pasting the finished file on top of the original (GPS intact file) and flattening, so that the finished file would take on the properties of the old, un-retouched file. What's odd about this is that after flattening the file, saving, and looking at File Info - it appeared it had WORKED. But when you close the file, and re-open, the GPS is gone again. -
GPS EXIF data removed when photos are synced to iPhone?
I have manually added GPS EXIF metadata to photos that were taken by an old camera.
After I synced these photos with iTunes for Win 11.3 to my iPhone all location data was gone.
Is this a known issue?
Your help is much appreciated!Nobody knows the answer? Yours was the third question like this I found by searching, yet none have been answered. I get the same results using Picasa. Once the photos are synced back to the iPhone, orientation is lost. Friends looking at the pictures on my iPhone have to keep rotating the device, cocking their head, or both. Some advanced device, that is!
-
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)... -
IPhoto for iOS removes the GPS exif data from the photo after an edit
iPhoto for iOS removes the GPS exif data from the photo after an edit
Using the iPhone camera, I take a photo and then I want to make the photo a little brighter.
So, I edit a photo using iPhoto for iOS and then save the photo back to the camera roll.
Now, I might want to see where that photo was taken via another app (like Photo Mapo) or on the map using the Photos app, or even the Mac iPhoto app.
However, the GPS data has been removed. Looks like all of the other exif data is still in the photo.
Why not just have a feature to remove the GPS data if the user wants? no reason to remove it for them.
The user explictily chose to have location services turned on so the GPS data would be in the photo.
Is this a bug?
Thanks,
Brian.First thing to try is a reboot of your iPad. Press and hold the Home and Sleep buttons simultaneously ignoring the red slider until the Apple logo appears. Let go of the buttons and let the iPad restart. See if that fixes your problem.
None of my cameras has a GPS function so I never see that data in the info of a photo in iPhoto for iOS. But I do see the map choice to set a location for the photo. Perhaps a reboot will fix this for you. -
IPhoto geotags not save in EXIF metadata
Why if I geotag a picture using iPhoto, that geotag won't be saved into the EXIF metadata? Exporting for example that picture in, say, Adobe Lightroom, or uploading it to Flickr won't show the location I picked in iPhoto, simply because that information is not stored in the EXIF metadata.
Is it this behaviour what iPhoto is supposed to do? Or is it a bug? Conversely, if I geotag a picture in Lightroom, that geotag will be saved in the EXIF metadata, and correctly read by any other applicationiPhoto stores the location data in the edited version and does not write it into the original image file. To create a geocoded image file, export the edited version with the location data included:
-
Missing Exposure EXIF Metadata After RAW Conversion
I am running Photoshop CS6 on a 64-bit Windows 7 PC. Since upgrading from CS5 I have noticed that the Exposure EXIF metadata as viewed in Bridge vanishes after RAW conversion/adjustment of my images. I've read at least one other posting to the forums describing a similar situation, however, I've not seen an acknowledgement of an issue or bug in Bridge. Clearing the RAW conversion settings restores the missing EXIF metadata.
Regards,
TonyQHave you seen this post? http://forums.adobe.com/thread/1014540?tstart=30
-
Index of EXIF-metadata from jpeg files by TREX
Hello,
I have the following scenario:
We have a central fileserver with a lot of marketing pictures. Our marketing people are looking for a solution to search pictures by data stored in the EXIF-metadata of the jpeg-files.
So I like to integrate this fileserver as a repository in KM, set up an index and let TREX do the search (as of note 663630 TREX can search the EXIF-Data of JPEG-Files).
As goodie I want to give the marketing people the possibility to browse through the pictures in an image gallery. This gallery should be consisting of a query-based taxonomy where all the pictures are sorted by special EXIF-data (e.g. name of the photographer).
Until now I have integrated the fileserver (as a FS-Repository) and create an index.
Before index creation I added the mime-type image/jpeg to the TREXValidMimeTypes.ini and restarted TREX.
After indexing the pictures could be found by its name, but the EXIF-data is not indexed.
Now my question:
Why TREX doesnt index the EXIF-metadata?
And how can I use the EXIF-data in an taxonomy?
System:
EP6.0 on WebAS 6.40 SPS16
TREX SPS16 Patch 2
KMC SPS16 Patch 2
Greetings from Berlin, Germany
JensGreetings to Berlin,
when triggered by KM, TREX will only index metadata that is known to KM as KM propertis.
I do not know in detail and am not at all sure, but you could try to create custom properties in KM that are called exactly like your EXIF-metadata, set them to "indexable", <b>not</b> fill them with values on KM side and then try again.
You may want to try this for just one of the EXIF-metadata as a test.
Even if that works somehow, the maximum result is:
- Property <b>name</b> existent in KM
- Property thus searchable an classifiable
- BUT property <b>values</b> will not show up in KM, as they will remain known only to TREX
Regards, Karsten -
Is there any way to set iPhoto 6 so that it will preserve all metadata in an image, even if the image is modified in iPhoto? It seems like the EXIF metadata is preserved in my photos upon import into iPhoto, but if I adjust an image using iPhoto all my EXIF metadata (shutter speed, aperture, etc.) is overwritten or lost.
This is very annoying. Why does iPhoto behave this way? It has no business overwriting this metadata that should, by all logical accounts in my mind, remain with the image.Jim:
How are you checking the metadata? I find that when I edit, like a crop, the modified jpg contains all of the EXIF data that the original has. I've verified that with other applications that read all the metadata.
The only metadata that is not saved for use by other applications are the comments and keywords. Those are kept in the iPhoto database file.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file. -
Problem with EXIF metadata reading
Hi everyone
I'm trying to read EXIF metadata information. Here is my code snippet:
uchar* exifData;
Handle exifDataHandle = filterRecord->handleProcs->newProc(100);
propSuite->getPropertyProc('8BIM', propEXIFData, 0, nil, &exifDataHandle);
exifData = (uchar*)(*exifDataHandle);
filterRecord->handleProcs->disposeProc(exifDataHandle);
After this code executed I have exifData size only 4 bytes, but as I now minimum valid EXIF data should be 6 bytes. Maybe I did something wrong?
Thanks for help.
RegardsDennis Knutson wrote:
The old serpdrv was eliminated with 7.0 unless you manually copied the VIs and driver from an older version.
Well perhaps it was I who converted in labview 5.1. I remember that the old system was quite clumsy written. It was very slow. But with a few trick it could be speeded up. Just by using refnums like in files and a simple C program for baud rate setting. I could use stable 115200 tranfer rates back in labview 3.1
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far) -
Can I change exif metadata with AIR?
Hi.
I am autor of a simple application that changes exif information in scanned images. I am looking for a way of re-implementing the application in a more cross platform way than it is today and found AIR interresting.
However, I can not find any API for accessing image metadata in the documentation..
Is altering the exif metadata possible with AIR (without having to implement all the "libexif-like" suff myself?)
Thanks
/sverrirThere is nothing built in to AIR - but you may wish to look at
http://code.google.com/p/as3corelib/
which is an opensource AS3 library which includes some image metadata manipulation routines.
You may also wish to make a feature request here
http://ideas.adobe.com/air
so that we will consider this addition in a future addition of the AIR runtime.
Hope that helps.
Chris Thilgen
AIR Engineering -
Lightroom Import: How to load Exif metadata description
Exif schema contains a description tag, which I would like to populate as part of the process of importing images from camera. Would you please show me how that can be done. I cannot locate rhe correct property in the import dialog.
Are you referring to the EXIF:ImageDescription field or the EXIF:UserComment field? When LR imports an image, those fields get automatically imported into the LR catalog. They appear in the Metadata panel on the right. EXIF:ImageDescription will be displayed as "Caption" under the Default metadata set, and EXIF:UserComment will be displayed as "User Comment" under the EXIF metadata set.
-
Hi,
how can i export all exif / metadata from an image to a txt/csv file?
I'm missing the copy & paste function for the metadata. If i edit an image with an external app, some of the exif data gets lost...
Cheers*missing the edit button*
I want to extract all the exif data (ISO, Aperture, Exposure, ...) I see inside Aperture.
And is there a way to write the exif (ISO, Aperture, Exposure, ..., NOT ONLY the subject, description, ...) from one image to a new image? -
How to make Canon specific EXIF metadata visible in LR?
Hi
I love LR but it excludes some fields of EXIF metadata that are provided by Canon's propietary raw converter. I am sure that there must be a way to make these visible inside LR so one can filter and create smart collections based on these metadata.
What is the best way to achieve this? A plug-in? Any additional info?
Thanks,
Juan DentOne possibility is to use Exiftool that can read Canon tags and transform it to keywords or captions that LR can understand. Check out this list from http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Canon.html:
Canon CameraSettings Tags
Index
Tag Name
Writable
Values / Notes
1
MacroMode
int16s
1 = Macro
2 = Normal
2
SelfTimer
int16s
3
Quality
int16s
1 = Economy
2 = Normal
3 = Fine
4 = RAW
5 = Superfine
130 = Normal Movie
4
CanonFlashMode
int16s
0 = Off
1 = Auto
2 = On
3 = Red-eye reduction
4 = Slow-sync
5 = Red-eye reduction (Auto)
6 = Red-eye reduction (On)
16 = External flash
5
ContinuousDrive
int16s
0 = Single
1 = Continuous
2 = Movie
3 = Continuous, Speed Priority
4 = Continuous, Low
5 = Continuous, High
7
FocusMode
int16s
0 = One-shot AF
1 = AI Servo AF
2 = AI Focus AF
3 = Manual Focus (3)
4 = Single
5 = Continuous
6 = Manual Focus (6)
16 = Pan Focus
9
RecordMode
int16s
1 = JPEG
2 = CRW+THM
3 = AVI+THM
4 = TIF
5 = TIF+JPEG
6 = CR2
7 = CR2+JPEG
10
CanonImageSize
int16s
0 = Large
1 = Medium
2 = Small
5 = Medium 1
6 = Medium 2
7 = Medium 3
8 = Postcard
9 = Widescreen
129 = Medium Movie
130 = Small Movie
11
EasyMode
int16s
0 = Full auto
1 = Manual
2 = Landscape
3 = Fast shutter
4 = Slow shutter
5 = Night
6 = Gray Scale
7 = Sepia
8 = Portrait
9 = Sports
10 = Macro
11 = Black & White
12 = Pan focus
13 = Vivid
14 = Neutral
15 = Flash Off
16 = Long Shutter
17 = Super Macro
18 = Foliage
19 = Indoor
20 = Fireworks
21 = Beach
22 = Underwater
23 = Snow
24 = Kids & Pets
25 = Night Snapshot
26 = Digital Macro
27 = My Colors
28 = Still Image
30 = Color Accent
31 = Color Swap
32 = Aquarium
33 = ISO 3200
38 = Creative Auto
261 = Sunset
12
DigitalZoom
int16s
0 = None
1 = 2x
2 = 4x
3 = Other
13
Contrast
int16s
0 = Normal
14
Saturation
int16s
0 = Normal
15
Sharpness
int16s
(some models use a range of -2 to +2 where 0 is normal sharpening, and others use a range of 0 to 7 where 0 is no sharpening)
16
CameraISO
int16s
17
MeteringMode
int16s
0 = Default
1 = Spot
2 = Average
3 = Evaluative
4 = Partial
5 = Center-weighted average
18
FocusRange
int16s
0 = Manual
1 = Auto
2 = Not Known
3 = Macro
4 = Very Close
5 = Close
6 = Middle Range
7 = Far Range
8 = Pan Focus
9 = Super Macro
10 = Infinity
19
AFPoint
int16s
0x2005 = Manual AF point selection
0x3000 = None (MF)
0x3001 = Auto AF point selection
0x3002 = Right
0x3003 = Center
0x3004 = Left
0x4001 = Auto AF point selection
0x4006 = Face Detect
20
CanonExposureMode
int16s
0 = Easy
1 = Program AE
2 = Shutter speed priority AE
3 = Aperture-priority AE
4 = Manual
5 = Depth-of-field AE
6 = M-Dep
7 = Bulb
22
LensType
int16s
--> Canon LensType Values
(this value is incorrect for EOS 7D images with lenses of type 256 or greater)
23
LongFocal
int16u
24
ShortFocal
int16u
25
FocalUnits
int16s
26
MaxAperture
int16s
27
MinAperture
int16s
28
FlashActivity
int16s
29
FlashBits
int16s
Bit 0 = Manual
Bit 1 = TTL
Bit 2 = A-TTL
Bit 3 = E-TTL
Bit 4 = FP sync enabled
Bit 7 = 2nd-curtain sync used
Bit 11 = FP sync used
Bit 13 = Built-in
Bit 14 = External
32
FocusContinuous
int16s
0 = Single
1 = Continuous
8 = Manual
33
AESetting
int16s
0 = Normal AE
1 = Exposure Compensation
2 = AE Lock
3 = AE Lock + Exposure Comp.
4 = No AE
34
ImageStabilization
int16s
0 = Off
1 = On
2 = On, Shot Only
3 = On, Panning
35
DisplayAperture
int16s
36
ZoomSourceWidth
int16s
37
ZoomTargetWidth
int16s
39
SpotMeteringMode
int16s
0 = Center
1 = AF Point
40
PhotoEffect
int16s
0 = Off
1 = Vivid
2 = Neutral
3 = Smooth
4 = Sepia
5 = B&W
6 = Custom
100 = My Color Data
41
ManualFlashOutput
int16s
0x0 = n/a
0x500 = Full
0x502 = Medium
0x504 = Low
0x7fff = n/a
42
ColorTone
int16s
0 = Normal
46
SRAWQuality
int16s
0 = n/a
1 = sRAW1 (mRAW)
2 = sRAW2 (sRAW) -
Lens Exif metadata worked for KM but no more for Sony cams
Playing with the metadata panel in Aperture 2.1, I was surprised to see the information for the lens manufacturer/model for some shots I did with my old Konica-Minolta 5D DSLR.
Sony took over the Konica-Minolta DSLR system about 2 years ago and as many others I have since moved to a Sony A100 body and recently to an A700 body.
Using the very same lenses, that give me detailed lens Exif metadata with the old Konica-Minolta 5D, the metadata field is empty with Sony A100 and A700 files.
A bit annoying, that the 4 years old Konica-Minolta 5D is supported in Aperture, while the follow up models from Sony are not.
Hope this will be fixed in the next update.
PeterSteve,
you are probably right, that Sony is encoding the lens data in a somewhat non standard way.
But as far as I know, in the EXIF of the Konica-Minolta files, this was done as well in a non standard way, by storing a binary lens code (at least I don't find any plaintext lens data in the image file, when I peek into it with a low level file-editor like Hexedit). As the lens information is displayed in clear text for the Konica-Minolta files within Aperture, Apple must have already integrated a lens database holding data for Konica-Minolta and Sony lenses. Interestingly even new Sony lenses like the Carl-Zeiss 16-80 lens show up, when used on an old Konica-Minolta DSLR.
For me it looks like Sony might store the same lens-code now in a different proprietary EXIF field but Aperture is still looking into the old Konica-Minolta EXIF field, which is non existent or empty.
So yes, Sony probably broke it, but there was enough time for Apple to fix it, especially as they have updated the lens database all the time. It is weired to add all recent Sony lenses to Aperture's lens database, but make the data only available, if you use the lenses on a 5 years old Konica-Minolta body.
So I repeat my request for Apple to fix this in Aperture soon.
Peter
Maybe you are looking for
-
How to activate the song, artist and album windows so you can type in those entries
how do you activate the windows for song, artist, album in iTunes library? I used to put the cursor over the category, double click on it, then type in the song name, artist name, album, genre etc., but that technique doesn't seem to work now.
-
Copying images with transparency produces a black background.
When images are copied from Firefox and pasted elsewhere (Paint, PSP, Photoship, etc.) any transparency becomes opaque black. This makes it difficult to edit the image if the transparency was near black pixels. Is there any way to change the colour t
-
just recently, I have tried to install iTunes. It gets about 85% complete, then throws a QuickTime error. The code is 2330 and after reading for a while the solution seems to be removing QuckTime from your system. Every time I try to do this, I get t
-
FF800 trouble since installing 8.0.1
Hi all, I am experiencing a really weird problem since upgrading to 8.0.1. The FireFace 800 driver goes all whacky, dropping out frequently, but only when Logic Pro is running (even without a project loaded). The Fireface is the Master clock, but it
-
IOS 4.3 confused lifetime call meter
I was looking around the setting etc after having upgraded the firmware, and I looked under General > Usage just for the **** of it. I saw that my call lifetime was in excess of 4 billion days. This isn't right. I only pay for 300 minutes a month and