run geosync windows : last reply in 2013

[h4n5]

Here's a question from a windows user - that's someone who can click on buttons, icons and hyperlinks but who has no knowledge how to run anything - although he picked up that you can 'run' things by typing CMD in the magnifying glass window, and to change the folder / directory you need by typing 'cd' followed be the letter assigned to that drive, perhaps followed by a / or \ .

What was done so far :
1/ Downloaded and extracted https://exiftool.org/exiftool-12.09.zip and removed the (-k) bit
2/ Inserted an SDHC card in the computer,
3/ copied the folder 201111test (contains copies of a couple of pics to be geotagged) ;
4/ also copied the following files :
201111.gpx (exported from Garmin Basecamp, based on the tracklog from an etrex10) ,
exiftool.exe and three nnn.jpg files which have a GPS location ;
5/ Found and read : https://exiftool.org/dummies.html and https://exiftool.org/geotag.html ;
6/ Based on example 13 on the latter page have 'written' : "exiftool -geotag 201111.gpx -geosync=G0029200.jpg -geosync=G0049730.jpg -geosync=G0060300.jpg /201111test"
7/ in Windows 10 (auto updated) clicked the magnifying glass icon bottom left, typed cmd , got a window w. black background and "Microsoft Windows [Version 10.0.19041.630]
(c) 2020 Microsoft Corporation. All rights reserved.  C:\Users\precus>"
8/ Typed cd H:\ , cd H:/ and cd H: in the hope that'd tell windows that all files are to be run from the card in that drive :

Question 1 : can one actually run exiftool from an SDHC card, or does it have to be somewhere on C:\ ?
Question 2 : would I then need to prefix the folder and each of the other files on the SDcard with H:\ ?
to make the above line into :  "exiftool -geotag H:\201111.gpx -geosync=H:\G0029200.jpg -geosync=H:\G0049730.jpg -geosync=H:/G0060300.jpg /201111test"   is there any difference between H:/ and H:\ in this respect?

Delving deeper see that I was able to install ExifToolGUI in C:\Program Files (x86)\ExifTool\exiftoolgui , and there's an exiftool.exe plus exiftool_files folder there.  That exiftool is v.12.07

Typing exiftool in the magnifying glass box yields
"NAME
    exiftool - Read and write meta information in files

RUNNING IN WINDOWS
    Drag and drop files or folders onto the exiftool executable to display
    meta information, or rename to "exiftool.exe" and run from the command
    line to access all exiftool features.

    This stand-alone Windows version allows simple command-line options to
    be added to the name of the executable (in brackets and separated by
    spaces at the end of the name), providing a mechanism to use options
    when launched via the mouse. For example, changing the executable name
    to "exiftool(-a -u -g1 -w txt).exe" gives a drag-and-drop utility which
    generates sidecar ".txt" files with detailed meta information. As
    shipped, the -k option is added to cause exiftool to pause before
    terminating (keeping the command window open). Options may also be added
    to the "Target" property of a Windows shortcut to the executable.

SYNOPSIS
  Reading
    exiftool [*OPTIONS*] [-*TAG*...] [--*TAG*...] *FILE*...

  Writing
    exiftool [*OPTIONS*] -*TAG*[+-<]=[*VALUE*]... *FILE*...

  Copying
    exiftool [*OPTIONS*] -tagsFromFile *SRCFILE* [-*SRCTAG*[>*DSTTAG*]...]
    *FILE*...

-- More  --"

Next attempt : with the window open and showing the instructions - even though -k removed from filename - copied/pasted the line with the H:s added : no result at all, not even an error

Question 3 : would exiftool still work under windows 10, please?

Those are my questions - for now, it'll likely be something dead simple, which may lurk on a page but no be obvious to someone who isn't versed in programming ...

Looking forward, met vriendelijke groet (Dutch for 'with friendly greeting),


= = = =

EDIT after cup of tea : the example line on https://exiftool.org/forum/index.php?topic=4888.0

     "A basic ExifTool command looks something like this:

         exiftool c:\pictures\image.jpg

     This command will display the metadata from the specified image."

produces what looks like relevant output :

"Microsoft Windows [Version 10.0.19041.630]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\precus>exiftool h:\G0029200.jpg
ExifTool Version Number         : 12.07
File Name                       : G0029200.jpg
Directory                       : h:/
File Size                       : 3.3 MB
File Modification Date/Time     : 2020:11:11 10:33:48+01:00
File Access Date/Time           : 2020:11:12 00:00:00+01:00
File Creation Date/Time         : 2020:11:12 11:24:30+01:00
File Permissions                : rw-rw-rw-
File Type                       : JPEG
File Type Extension             : jpg
MIME Type                       : image/jpeg
Exif Byte Order                 : Big-endian (Motorola, MM)
Image Description               : DCIM\100GOPRO\G0029200.JPG
Make                            : GoPro
Orientation                     : Horizontal (normal)
X Resolution                    : 72
Y Resolution                    : 72
Resolution Unit                 : inches
Software                        : HD9.01.01.22.00
etc. etc. etc. "

It's just that the line which I composed -see above, irrespective of // or \\\, doesn't do any trick, let alone geotag images which were not geotagged in the GoPro Hero9 , and that concerns some 6056 out of a sequence of 21132 pics : obviously worth the while getting this to work.

And to people who ask "why do you need ... ?": now retired as a consulting engineer, like to walk and ride bicycle, learned about OpenStreetMap (OSM), started adding notes with points to improve, was asked to provide photos, worked out that the Hero would be just the thing to record 'everything' along the track, pics can then be uploaded to a site in Sweden which first blurrs faces and number plates, then extracts traffic signs and larger features such as fuel stations and roundabouts for routing apps,  and finally makes the pics available to OSM editors, 'normalised' by pointing each photo at the next, which helps mappers work out wht they're looking at.

[StarGeek]

Question 1 : can one actually run exiftool from an SDHC card, or does it have to be somewhere on C:\ ?

Exiftool has to be in what's called the PATH, which is a list of all the directories that Windows will look through when it looks for a command.  I think you can see the full list by typing path into the CMD window (at least it can on my system, though it might be something that was added). It will be a wall of text, though.

Helpful hint, CD by itself won't change the directory to another drive.  You would either change the drive by just typing the drive name, i.e. type H:\ to switch to the H:\ drive and then cd from there, or by adding /d to the cd command, i.e. type cd /d H:\

Question 2 : would I then need to prefix the folder and each of the other files on the SDcard with H:\ ?
to make the above line into :  "exiftool -geotag H:\201111.gpx -geosync=H:\G0029200.jpg -geosync=H:\G0049730.jpg -geosync=H:/G0060300.jpg /201111test"   is there any difference between H:/ and H:\ in this respect?

If H:\ wasn't the current directory, then yes, you would have to prefix the path.  It's all a matter of preference.  I tend to stay in the home directory and copy/paste the drive paths, but then I have a lot of tools installed to help with that.  Another hint is that typing a single dot indicates the current directory.

For exiftool, there's no difference between H:/ and H:\.  Perl, the language that exiftool was created with, treats H:\ as H:/ internally.  But for any other CMD program, it's more likely that slashes / may cause problems.

Delving deeper see that I was able to install ExifToolGUI in C:\Program Files (x86)\ExifTool\exiftoolgui , and there's an exiftool.exe plus exiftool_files folder there.  That exiftool is v.12.07

Question 3 : would exiftool still work under windows 10, please?

Exiftool does work under Windows 10.  The ExiftoolGUI may not.  The author of the GUI has not been supported it for eight years.  It does not work at all for me.  But there is a new java based gui.  Take a look at hvdwolf's jExifToolGUI.

Those are my questions - for now, it'll likely be something dead simple, which may lurk on a page but no be obvious to someone who isn't versed in programming

Searching for some command line tutorials is always helpful.  Especially if you add something like ELI5 (which stands for Explain it Like I'm 5) to your search questions.