Same script, same images, new errors

[Happy Hobo]

Directory 20190412 contains 72 files matching *.jpg

Script GPX contains the command

Code Select Expand

  exiftool --ext csv --ext gpx --ext pdf --ext html --ext zip \
           -api filter="s/^\+//" \
           -p   ~/bin/gpxl.fmt   \
           -userparam name="$3"  \
           -userparam desc="$4"   *.jpg  >  /tmp/${2}-l.gpx
~/bin/gpxl.fmt includes the line

Code Select Expand

#[BODY]        <time>${datetimeoriginal#;DateFmt("%Y-%m-%dT%H:%M:%S");}</time>
None of these three files had been changed for months.

Starting today, GPX 20190412 gets numerous errors like:

Code Select Expand

Warning: ValueConv GPSTimeStamp: Argument "2019-04-12T13:26:01.96+0000" isn't numeric in multiplication (*) - 20190412_152602.jpg
By adding exit statements before and after, I determined that the above command is the first one to get those errors.  But it only gets 51, not 72

I look at the .gpx file created, and it contains 64 trackpoints—neither 51 nor 72.

When I remove the timestamp line from the format file, I still get the multiplication errors.

I am baffled.

[StarGeek]

Same version of exiftool?

Edit: Can you create a CSV file from you 72 files with this command
exiftool -G1 -a -s -csv -exif:gps* -EXIF:time:all /path/to/files/ >file.csv

And this zip that together with GPX.fmt file and attach it here? The reason I ask for a zip file is to make sure the file is exactly the same. If you copy/pasted it to the forum, the forum might change some characters.

That way I can try and replicate your test environment and take a closer look.

[Phil Harvey]

This will happen if GPSTimeStamp has been written incorrectly as the string "2019-04-12T13:26:01.96+0000" instead of the specified 3 rational values.  I have no idea how this could happen.  Some other misbehaving software I would think.  To do this with ExifTool would require using a badly written config file.

But this is only a warning so the affected files will still be processed, and it will only affect the value of GPSTimeStamp which you probably aren't using.

- Phil