When trying the new mapping feature with a set of vacation pictures that were tagged by GeoSetter I find they all display at a common but incorrect position. A mouse-over of the green marker shows the location to be at an even degree, all numbers following the decimal have been removed.
A pictured tagged by ExiftoolGUI displays at the correct location in GeoSetter but not in ExiftoolGUI.
Repeatable on both Win 7-64 and XP-32
Hal
Agree with OP above. Also I can only get the Map button to show by first selecting Various/Google Map which brings up Google Map centred on Maribor even though I have input my own location. I would prefer Google Map to come up centred on selected photo not Home place if possible.
To
32110:
Yes, when map is showing the first time (in GUI session), then it's centered "somewhere" (Maribor in this case). Now only the click on Home button is needed for jump to your predefined (home) location, or.. every click on Map>> button (below Custom view button) will show geo-position of the photo on the map (if file contains gps data).
I'm aware, that clicking on Map>> button for each (of many) photo isn't very user friendly... It can be done better, so each photo selection in filelist automatically updates map content -no problem for those who have hi-speed internet access. But I don't know how everything would behave on slow speed... I'll try to make "faster" as an option and then we will see.
To
Hal:
Quotea set of vacation pictures that were tagged by GeoSetter I find they all display at a common but incorrect position.
You mean: ...tagged by GeoSetter, they show correctly inside GeoSetter, but not in GUI?
QuoteA pictured tagged by ExiftoolGUI displays at the correct location in GeoSetter but not in ExiftoolGUI.
Can you give coordinates example for such behaviour? -whole image file would be much better (the same for file where decimal places are missed).
Another thing I maybe didn't emphasized enough (even I don't know if that matter in this case): as mentioned in manual, for geotagging and viewing on map, GUI uses Exif GPS metadata only! -no XMP metadata.
Bogdan
Bogdan, thanks for reply. Have attached photo from Berlin that you can try.
Photo geotaged with GPicSync.
Further to my previous reply. The location of photos appears to be a Google Earth problem. When I drop my photo onto Google Earth the Lat/Lon co-ordinates are rounded to exact degrees with no decimals. But if I drop this photo (attached) it locates correctly.
Very odd. One difference I see is that the 2nd image you posted (the one that works) is GPSVersionID 2.3.0.0, while the bad one is 2.2.0.0. I wonder if this could be the difference when loaded in Google Earth.
Also, the GPSLatitude/LongitudeRef values are written incorrectly in both images. There is an extra null byte that shouldn't be there. This is unrelated to your problem, but it indicates that ExifTool did not write this GPS information.
- Phil
Phil/Bogdan, First photo tagged with GPicSync second with GeoSetter both of which use ExifTool some how or other.
Sorry, My mistake both photos tagged with GPicSync
I have tried both photos. Here:
1st photo (Berlin -no doubt) is shown on map correctly: Berlin.
2nd photo (boat -I don't recognize the place) is shown near Hastings (south England) -is that the place?
In both cases coordinates (decimal) in Exif and on the map seems to be equal...
Bogdan
PS: I've zoomed the map and 2nd photo seems to have correct coordinates as well.
Yes 1st photo Berlin, 2nd Hastings. Attachment shows placement of the Berlin one that I get using ExifToolGUI. You will note that by hovering mouse over point the co-ordinates have been truncated with no decimal places.
This picture was taken in The Pinery Provincial Park (South of Grand Bend) but is shown East of London Ontario. All decimal places are in the exif data but at location, as shown by the green marker, they are missing. I have tried random pictures from thousands geotagged by GeoSetter with the same results, all display correctly in GeoSetter
I see what you mean... but that doesn't happen here -here, I can see decimal places in hover coordinate info.
Holly crap... I see now why this happens... Your PC regional settings: you're using "," as thousands separator and "." (=dot) as decimal separator, right? Here, in Europe, opposite is the case... and as it seems (my guess), Google checks your regional position (according to IP) and translates decimal sign from "." to "," (and vice versa).
I must do something about this, of course. It's getting very late here... I will be back tomorrow.
Bogdan
Bogdan - I am also in Europe, UK in fact but it is usual for us to use . as decimal and , as thousands seperator. Lets hope you are onto something but to bed first! :)
Just a quick report.. this decimal issue has nothing to do with GoogleMap. It is my compiler's "feature" which I need to correct.
Update: New GUI version (v4.12.1.0) is ready for download -geopositioning should now work as expected.
Thank you for guiding me toward solution.
Bogdan
Agreed - GPS items now working as described in latest release note. Very many thanks Bogdan, I'm pleased that you were able to spot your compiler's useful "feature" so quickly.
Much improved, thank you. I had been ready to claim that the values were still being changed somewhat but just before posting I noticed they agree with those shown in Quick mode. This resulted in a shift of 2Km from the actual location on the picture I was testing with
As I never use the Quick mode I had not noticed before that there is no longitude displayed, could this be a problem with our negative value
I love ExiftoolGUI for its original purpose, to provide an easy way to harness the power of Exiftool... keep up the good work
Hal
Hi Hal,
Quote...This resulted in a shift of 2Km from the actual location on the picture I was testing with
-I'm confused.. is it OK now, or is there still some (2Km) problem with v.4.12.1?
About Longitude not being shown in Quick mode... :) The thing is I've used (shown) Latitude value in Quick view for my programming needs -for easier locating where decimal digits truncation occurs in GUI. That is, it's not that Longitude is somehow "missing" in Quick view, in contrary: Latitude shouldn't be there -I've forgot to remove that entry when I've made final compilation.
As I've mentioned elsewhere before, Quick view is ment for displaying only most essential metadata tags in high(er) speed. For that purpose I have "invented" Geotagged entry there, which only tells if image is Exif geotagged or not -actual values are not that important for "quickie". If needed, they can be seen/checked in
Exif or
Custom view mode. What I'm trying to say is: Latitude value won't be displayed in next GUI release.
And about "coordinate in Quick view not having negative value"... In Exif, negative coordinates doesn't exist -there are separate tags (LatitudeRef and LongitudeRef which serve that purpose). However, when "sent" from GUI toward GoogleMap, coordinates are first signed as needed, because GoogleMap expects signed coordinates.
A bit longer explanation, but I think, sometimes, it's good to know some "background" -and I have a chance for my English training :)
Bogdan
I am seeing an error still, 2Km in the test picture but many are less. The value shown by the map pointer is the same as the latitude value shown in Quick view. This value is not the same as what shows in Exif view and seems to be limited to 2 decimal places or end in a repeating 3 or 6
I have attached a screen capture showing the exif gps coordinates and those reported by the map. The correct location is at the bridge just to the north
Now I am confused! I just manually geotagged an image using ExiftoolGUI and it displayed properly, returning again to the others they are also in the proper locations? Whatever the problem this one seems to have been in my computer
You just saved my day :)
Did you perhaps changed between GUI versions inbetween? Anyway, if you notice any strange behaviour, feel free to report.
Bogdan
I changed to the new version yesterday and did the screen capture then, after being powered down for the night I saw the same strange results this morning before posting. The first attempt at geotagging with the new version produced a picture that showed normal looking latitude in quick view and located properly on the map. From then on all old pictures have worked as well. Looking back it felt like I had been reusing cached data but I did not think your program used a cache
Once again Thank You
Hal