Problem with GPS data in IM5

[emef]

Hello everyone,
I have a problem (I do not really understand) with GPS data in IM5; it seems qu'IM5 lose my data nrw files (or nave) when I click the blue globe: "Map" window opens and the red flag is in the ocean in the African continent. This occurs only for "raw", not jpeg.
Similarly, if instead of clicking on the globe, I display metadata, open the tab "location" let me see the information surreptitiously three lines GPS (latitude, longitude and altitude), so those seem entirely smoothly erased and replaced by green lines without any indications, and in the window showing the pictures, blue globe disappeared. Always only for "raw", jpeg appear unaffected.
I note the gps data with either my Garmin Oregon 550T or with my smartphone and an application such as "Lotus Pro" or "Geotag Photos Pro"; in all cases in the format "gpx" and I run either "GPSync" or "GeoSetter" to fill the gps data of these photos.
Under Ligthroom, everything seems to work and the "Map" tab shows me my good shots where it should appear.
In "Metadata 2", I configured "IPTC Timezone" and "EXIF Timezone" with "+01:00".
Sorry for being a bit long, and my English is provided to me by a friend Google   
Thank you in advance.

[Mario]

IMatch imports GPS data from EXIF into XMP, and displays the GPS tags from XMP in the metadata panel.

Do you files contain GPS data in EXIF?
Do your files contain GPS data in XMP?
Have your files XMP data embedded in the NEF?
Have your files a sidecar XMP file?

[emef]

My apologies, I cried before he felt the blows.   

After checking my XMP and my exif, I appercu these files contained no information on the GPS data.
Since it worked in Lightroom, I simply pressed the option to save the data in the files and then GPS coordinates appear well in IM5, and this time seem to stay there.

But I just perceive me as if the GPS data is displayed well in the Metadata panel in the "Location" position ** it does not appear in "Default" (everything is under GPS is indicated at 0 degrees - see jpeg).
As in "Image Info", everything in the GPS part is set to 0 (marked with a blue cross a padlock), but it may be normal?

[** In the "Location" tab - see jpg 2, the latitude and longitude appear fine but the information such as "ISO Country Code, Country, State / Province, City, and Location" remain empty. How can I fix this other than doing it manually?]
Thank you again for your patience, as I am sure most of the problems that I recall from my ignorance of the software but also how to manage metadata in general.   



[attachment deleted by admin]

[Mario]

The "Default" metadata panel uses the GPS data contained in the XMP-exif namespace.
The "Location" sample metadata panel layout uses the same XMP fields. There is (usually) no difference between the two.

If a file contains GPS data in the EXIF record, IMatch fills these XMP tags from the existing EXIF data (if MWG compliance is on).
If a file has no EXIF GPS data, IMatch uses whatever data is in these XMP tags.

When you modify GPS data in IMatch (via the Map panel or one of the other features), IMatch updates the XMP-exif GPS tags. When IMatch writes back metadata to your files, it writes the XMP and then also updates the EXIF record in your image (if there is one) from that data.

I would need a sample NEF file and the matching XMP file (if you have one) to analyze this further. This usually just works, as long as all applications who have created/modified GPS data play by the rules.

[emef]

My nef file (NRW) is 27 megas, how can I send it to you (the lowest I get is ZIP 17.7 million) ?   

[Mario]

If you have no cloud storage, please contact me via my support email.
You can send me the file via email if your ISP allows for such large files (see my address details below).
Or contact me and I will send you credentials for my FTP server where you then can upload the file.

[emef]

I would have thought (age, memory, Alzheimer ... all)     

https://dl.dropboxusercontent.com/u/16329473/emef_20140601_DSCN1790.zip

[Mario]

Very well. Thanks for the sample.

The problem is clear:

1. The NEF file contains GPS data

[GPS]           GPS Version ID                  : 2.3.0.0
[GPS]           GPS Latitude Ref                : Unknown ()
[GPS]           GPS Latitude                    : 0 deg 0' 0.00"
[GPS]           GPS Longitude Ref               : Unknown ()
[GPS]           GPS Longitude                   : 0 deg 0' 0.00"
[GPS]           GPS Altitude Ref                : Above Sea Level
[GPS]           GPS Altitude                    : undef
[GPS]           GPS Time Stamp                  : 00:00:00
[GPS]           GPS Img Direction Ref           : Unknown ()
[GPS]           GPS Date Stamp                  : 0000:00:00
[IFD0]          Date/Time Original              : 2014:06:01 11:03:04


and this is what IMatch uses. The XMP record you have for your file contains totally different GPS coordinates. But the GPS coordinates embedded in the NEF file override the GPS coordinates in the XMP in IMatch.

When I remove the invalid GPS data from the NEF file with the ExifTool Command Processor in IMatch, the GPS data in the XMP is used and the coordinates show up in IMatch.

That's the solution for your problem: Remove the invalid GPS data from the NEF file in the ECP. Try this for one of your files:

1. Select the NEF
2. Open the ECP with <F9>,<E>
3. Copy/Paste these commands:

-overwrite_original_in_place
-gps:all=
{Files}


4. Run the command with <F9>

Close the ECP. IMatch will reload the NEF and show the coordinates read from the XMP file, which are now no longer masked by the invalid GPS data in the file.

[emef]

Mario thank you, it works. 

But there is something I do not understand: before starting ECP command on the nave, the exactent details appear well in the Panel "Metadata / Location", so it is that Imatch has in his possesion (in that these pictures are well positioned on the map). So why is it necessary to run this command for IM5 can fill all the fields of all metadata? 

[Mario]

There is no difference. Both the Default metadata panel layout and the Location layout use the same tags. At least in the layouts I ship with IMatch.
Do you use the standard layouts? Maybe you have old layers from an old Beta?



Check the tags (tooltips!) used by your Location layout. The location layout I ship uses

XMP::exif\GPSLatitude\GPSLatitude\0
XMP::exif\GPSLongitude\GPSLongitude\0



[attachment deleted by admin]

[emef]

Ok Mario, I applied your settings, both in layout "location" and "metadata templates" ... Maybe this is it redundant?   

[Mario]

I don't understand.

Metadata Templates allow you to fill metadata tags with data.
Metadata Panel layouts allow you to customize which metadata you see.
The default layouts IMatch ships with use only XMP data because that is the 'safe' data.

[emef]

I do not quite understand what you do not understand       

But even if it is redundant, it seems to have no negative effect on the results of my way to work. By against a thing that I noticed in the panel "Metadata / Core Data / description": if I add a text and I save the changes, the yellow pencil appears and when I click on pencil data should be registered. Now when I open again "Metadata / Core Data / Description" field is empty, I have to click on the side arrow to choose again (among others) the text I took the step previous. By cons, if I do "Ctrl-Alt-S", the entered text appears immediately, without having to click on the yellow pencil; I guess it has to do with my choice of "Metadata Write Back"?

[Mario]

Ok Mario, I applied your settings, both in layout "location" and "metadata templates" ... Maybe this is it redundant?   

You refer to location and metadata templates and then speak about redundancy. What is redundant?
The Metadata panel sample layout "Location" combines several of the location tags together. While the "Default" layout shows metadata tags in a format similar to what users know from software like LR. Where is there something redundant?

Metadata Templates are not about viewing metadata but automatically filling in metadata.

[Mario]

By against a thing that I noticed in the panel "Metadata / Core Data / description": if I add a text and I save the changes, the yellow pencil appears and when I click on pencil data should be registered. Now when I open again "Metadata / Core Data / Description" field is empty, I have to click on the side arrow to choose again (among others) the text I took the step previous. By cons, if I do "Ctrl-Alt-S", the entered text appears immediately, without having to click on the yellow pencil; I guess it has to do with my choice of "Metadata Write Back"?

When you change the description tag in the Default metadata panel layout, IMatch marks the file as pending. When you click on the pencil or use one of the commands to write-back pending metadata, IMatch updates the file.

In case of the description, IMatch updates the XMP-dc:Description tag. Since the MWG demands that this is also mirrored to other metadata standards, e.g. IPTC, the IPTC:Caption/Abstract tag is also updated.

The typical problem when data does not stick is when users mix metadata from different standards and don't allow IMatch to update all data during a wriite-back.
You did not mention which file formats you use or which metadata settings you use so I can only work with incomplete information here.

A typical case would be:

You work with RAW files.
You keep XMP metadata in XMP sidecar files.
But your RAW files have embedded legacy IPTC data, or XMP data, or both.
Your metadata settings do not allow IMatch to update the data in the file.

The result of this is:

IMatch writes the new description into the XMP sidecar file.
It then re-imports the data from the file, applying the MWG rules and thus mapping existing IPTC, EXIF, GPS data into XMP. And this will erase the new description, because IMatch has not updated the IPTC data in the file during the write-back because it was not allowed to.

To analyze your bug report:

1. Provide details about file formats used and your metadata settings
2. Append a log file from a session where you reproduced the problem
3. Open the ExifTool output panel (<F9>,<O>) and do a write-back
4. CopyPaste the contents of the output panel to your reply.

[emef]

My photo formats are raw (nef and nrw) and some pictures have already been developed in jpeg before cataloging in IM.


Here is the output ExifTool:

«  ----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg

----- Runtime: 0,0 s.
Warning: Error converting value for ExifIFD:SubSecTimeOriginal (ValueConvInv) - E:\Photos\2014-03-20\emef_20140320_DSCN1749_sepia.jpg »

The error this time seems to involve only the jpeg format.


[attachment deleted by admin]

[Mario]

That warning/error is normal when no sub-second resolution data is available in your files.

[emef]

Oups !
My metadata settings :

[attachment deleted by admin]