RubyGems - exiftool_vendored - Versions diffs - 10.04.0 → 10.23.0 - Mend

exiftool_vendored 10.04.0 → 10.23.0

Potentially problematic release.

This version of exiftool_vendored might be problematic. Click here for more details.

Files changed (1225) hide show

data/bin/Image-ExifTool-10.04/html/filename.html DELETED Viewed

@@ -1,352 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-        "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
-<html>
-<head>
-  <title>FileName and Directory tags</title>
-<link rel=stylesheet type='text/css' href='style.css' title='Style'>
-<style type="text/css">
-<!--
-.prog    { padding: 0.5em; border: 1px solid gray; background: #fee }
--->
-</style>
-</head>
-<body>
-<h2 class='up'>Writing "FileName" and "Directory" tags</h2>
-<p>By writing the <b>FileName</b> and/or <b>Directory</b> tags, ExifTool can be
-used to rename and/or move images into directories according to any information
-contained in the image.  This is a powerful feature when combined with the
-<code>-tagsFromFile</code> ability to copy the values from other tags.  The most
-common use of this feature is to organize images by date/time, but any other tag
-value may also be used.</p>
-<p>Writing the <b>Directory</b> tag moves a file to a specified directory.  The
-directory is created if it doesn't already exist.</p>
-<p>Writing the <b>FileName</b> tag renames a file.  If the new <b>FileName</b>
-has a directory specification (ie. contains a '<code>/</code>' character), then
-the file is also moved to the specified directory (see
-<a href="#ex6">example 6</a> below).  Existing files will not be overwritten
-(but see "Warning" below).</p>
-<p>The write-only <b>TestName</b> tag provides a mechanism for dry-run testing
-of the rename feature.  Writing <b>TestName</b> displays the old and new names
-without making any changes to the files.  (Note that there is no corresponding
-test tag for <b>Directory</b>, but <b>TestName</b> supports a full path name
-just like <b>FileName</b>, so the directory may be tested as well.)</p>
-<p>The <code>%d</code>, <code>%f</code>, <code>%e</code> file name format codes
-may be used to represent the directory, name and extension of the original file
-when specifying <b>FileName</b> and <b>Directory</b> tags via the command-line
-interface. (In a similar way to the <code>-o</code>, <code>-w</code> and
-<code>-tagsFromFile</code> options.) Also, <code>%c</code> may be used to add a
-copy number to the output file name to avoid collisions with existing file
-names. Note that these codes must be escaped with an extra <code>%</code> if
-used within a date format string.  Modifiers may also be used to change the
-default behaviour of these format codes.  See the <code>-w</code> option in the
-<a href="exiftool_pod.html">application documentation</a> for details.</p>
-<p>When organizing files by date/time, use of the <code>-d</code> (date format)
-option is essential to specify a format for the filename (and/or directory
-name).  The examples below demonstrate the use of this feature.  Also, a list of
-of <a href="#codes">common date format codes</a> is provided for reference.</p>
-<blockquote class=prog><b class=red>Advanced feature:</b> The write-only
-<b>HardLink</b> tag may be written using a technique similar to <b>FileName</b>.
-Instead of renaming or moving the file, writing <b>HardLink</b> creates a hard
-link with the specified name.  This feature allows files to be organized without
-affecting the originals.  See the <a href="TagNames/extra.html">Extra Tags
-documentation</a> for more information.</blockquote>
-<h3>Notes:</h3>
-<p>Writing the <b>FileName</b> and/or <b>Directory</b> tags alone causes the
-file to be renamed or moved, not copied.  However, if any "real" tags are
-written at the same time, then the file is rewritten to the new destination and
-the original file is left unchanged.  (Only the four writable "pseudo" tags,
-<b>FileName</b>, <b>Directory</b>, <b>FileModifyDate</b> and
-<b>FileCreateDate</b>, may be set without causing the file to be rewritten.)  If
-desired, the <code>-overwrite_original</code> option may be used to remove the
-original copy when the file is rewritten.</p>
-<p>Conversely, the <code>-o</code> option may be used to force exiftool to
-always create a copy of the file, even if no meta-information tags are written.
-This is true even if the <code>-o</code> option is superseded by writing the
-<b>Directory</b> tag, or through a <b>FileName</b> which includes a directory
-specification.  (See <a href="#ex5">example 5</a> below.  Also see
-<a href="#ex11">example 11</a> for the directory precedence rules.)</p>
-<p>If the <code>-d</code> option is used, the unformatted date/time value must
-be valid (ie. in the form "<code>YYYY:mm:dd HH:MM:SS</code>"), otherwise the
-date formatting will fail and the file will not be renamed or moved.</p>
-<p>In a Windows batch file, all <code>%</code> characters must be escaped as
-<code>%%</code>.  This can result in extreme format codes like
-<code>%%%%f</code> when using the <code>-d</code> option.</p>
-<blockquote class=prog><b class=red>Warning:</b>
-Writing <b>illegal file names</b> in Windows can have unpredictable results and
-may result in <b>data loss</b>.  Illegal characters in Windows file names are:
-<pre class=code>    / \ ? * : | " &lt; &gt;</pre>
-Any tag used in generating a file name which may contain these characters must
-first be filtered to remove or translate these characters.  A special feature
-allows these characters to be removed from a tag value by adding a semicolon
-inside the braces after a tag name.  For example:
-<pre class=code>    exiftool "-filename&lt;${model;}.%e" c:\images</pre>
-This advanced formatting feature may also be used to do arbitrary reformatting
-of any tag value used in a format string.  See the <code>-p</code> option in the
-<a href="exiftool_pod.html">application documentation</a> for more details.
-</blockquote>
-<h2>Examples</h2>
-<a name="ex0"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;0.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -d %Y%m%d_%H%M%%-c.%%e "-testname&lt;CreateDate" DIR
-</code></td></tr></table>
-<blockquote>
-The <b>TestName</b> tag is used for dry-run testing of the file renaming
-feature.  The above command is identical to that of the next example except that
-<b>TestName</b> is written instead of <b>FileName</b>.  So instead of renaming
-the files, this command prints the old and new file names without actually
-changing anything.  For example:
-<blockquote><pre>&gt; <span class=code>exiftool -d %Y%m%d_%H%M%%-c.%%e "-testname&lt;CreateDate" tmp</span>
-'tmp/a.jpg' --&gt; 'tmp/20031031_1544.jpg'
-'tmp/b.jpg' --&gt; 'tmp/20010519_1836.jpg'
-    1 directories scanned
-    0 image files updated
-    2 image files unchanged</pre></blockquote>
-</blockquote>
-<a name="ex1"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;1.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -d %Y%m%d_%H%M%%-c.%%e "-filename&lt;CreateDate" DIR
-</code></td></tr></table>
-<blockquote>
-Rename all images in directory '<code>DIR</code>' to names like
-'<code>20060327_1058-2.jpg</code>', with individual file names derived from the
-value of the CreateDate (plus a copy number with a leading '<code>-</code>' if a
-file with the same name already exists), and with the same extension as the
-original image.  <i class=lt>[Note that copying tag values with '<code>&lt;</code>' implies
-'<code>-tagsfromfile @</code>' unless otherwise specified.  See the
-<code>-tagsFromFile</code> description in the
-<a href="exiftool_pod.html">application documentation</a> for details.]</i>
-<p><b>FAQ:</b> <i>"Why doesn't this command rename my files?"</i></p>
-<p>There are 2 common reasons for this:</p>
-<p>a) When a directory name is specified, this command will only rename "writable"
-files in the directory.  Use '<code>exiftool -listwf</code>' to list the
-extensions of currently writable file types.  The <code>-ext</code> option may
-be used to rename other file types (eg. '<code>-ext avi</code>').</p>
-<p>b) For this command to work, the CreateDate tag must exist in the source
-file. Use '<code>exiftool -createdate FILE</code>' to see if a file contains
-this information.  If it doesn't, you may need to use another date/time tag such
-as DateTimeOriginal or FileModifyDate.  To see all available date/time tags in a
-file (and their locations), use '<code>exiftool -a -G1 -s -time:all FILE</code>'.</p>
-</blockquote>
-<a name="ex2"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;2.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -d %Y-%m-%d "-directory&lt;datetimeoriginal" image.jpg
-</code></td></tr></table>
-<blockquote>
-Move '<code>image.jpg</code>' into a directory with a name given by
-DateTimeOriginal, in the form '<code>2006-03-27</code>'.
-</blockquote>
-<a name="ex3"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;3.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool '-filename&lt;%f_$imagesize.%e' dir
-</code></td></tr></table>
-<blockquote>
-This example uses an expression to add the image size to the name of all images
-in directory '<code>dir</code>'. For example, this would remame a 640x480 image
-called '<code>image.jpg</code>' to '<code>image_640x480.jpg</code>'. (Note that
-the single quotes are necessary in Unix shells due to the '<code>$</code>'
-symbol, but double quotes must be used instead when running in a Windows cmd shell.)
-</blockquote>
-<a name="ex4"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;4.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -r -directory=%e_images/%d pics
-</code></td></tr></table>
-<blockquote>
-Recursively move all images based in directory '<code>pics</code>' to
-separate directory trees organized by file extension.  For instance, in this
-example the file '<code>pics/toys/new_car.jpg</code>' is moved to
-'<code>jpg_images/pics/toys/new_car.jpg</code>'.
-</blockquote>
-<a name="ex5"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;5.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -r -o %e_images/%d pics<br>
-exiftool -r -o dummy/ -directory=%e_images/%d pics
-</code></td></tr></table>
-<blockquote>
-Both of these commands have the same effect as example 3 above except that
-images are copied instead of moved since the <code>-o</code> option was used. In
-the second command the trailing '<code>/</code>' on '<code>dummy/</code>' is
-necessary because otherwise '<code>dummy</code>' would be interpreted as a file
-name.  This technique of using <code>-o</code> with a dummy directory name is
-necessary when the directory name is derived from the value of other tags (eg.
-'<code>-directory&lt;createDate</code>') and you want the files to be copied
-instead of moved.  (Because the values of other tags may not be used with the
-<code>-o</code> option.)
-</blockquote>
-<a name="ex6"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;6.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -r -d %Y/%m/%d/image_%H%M%S.%%e "-filename&lt;filemodifydate" DIR
-</code></td></tr></table>
-<blockquote>
-Recusively rename all images in '<code>DIR</code>' and any contained
-subdirectories to the form '<code>image_HHMMSS.EXT</code>' (where
-'<code>ext</code>' is the original file extension), and move them into a new
-directory hierarchy based on date of file modification, with path names like
-'<code>2006/03/27/image_105859.jpg</code>'.
-</blockquote>
-<p>The following examples demonstrate the interaction of this feature with
-other ExifTool options:</p>
-<a name="ex7"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;7.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -filename=new.jpg dir/image.jpg
-</code></td></tr></table>
-<blockquote>
-Rename '<code>dir/image.jpg</code>' to '<code>dir/new.jpg</code>'.
-</blockquote>
-<a name="ex8"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;8.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -filename=new.jpg -comment=xxx dir/image.jpg
-</code></td></tr></table>
-<blockquote>
-Copy '<code>dir/image.jpg</code>', add a new comment, and write output to
-'<code>dir/new.jpg</code>'. The original file '<code>dir/image.jpg</code>' is
-not changed.
-</blockquote>
-<a name="ex9"></a><table cellpadding=6>
-<tr><td valign='top'>&nbsp;9.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -filename=new.jpg -comment=xxx -overwrite_original dir/image.jpg
-</code></td></tr></table>
-<blockquote>
-Rewrite '<code>dir/image.jpg</code>', adding a new comment and writing output to
-'<code>dir/new.jpg</code>'. The original file '<code>dir/image.jpg</code>' is
-removed.
-</blockquote>
-<a name="ex10"></a><table cellpadding=6>
-<tr><td valign='top'>10.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -o tmp/ -filename=new.jpg image.jpg<br>
-exiftool -o tmp/xxx.jpg -filename=new.jpg image.jpg<br>
-exiftool -o tmp/new.jpg image.jpg
-</code></td></tr></table>
-<blockquote>
-A file name or directory specified via the <b>FileName</b> or <b>Directory</b>
-tag takes precedence over that specified by the <code>-o</code> option, so these
-three commands all have the same effect: '<code>tmp/new.jpg</code>' is created
-without changing '<code>image.jpg</code>'.  Note that in the first command, the
-trailing '<code>/</code>' on '<code>tmp/</code>' is necessary if the
-'<code>tmp</code>' directory doesn't already exist, otherwise '<code>tmp</code>'
-would be taken as a file name and '<code>new.jpg</code>' would be created in the
-current directory.  As illustrated in example 4 above, the file is rewritten
-instead of simply being renamed when the '<code>-o</code>' option is used.
-</blockquote>
-<a name="ex11"></a><table cellpadding=6>
-<tr><td valign='top'>11.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -directory=dir1 -filename=dir2/out.jpg -o dir3/ dir4/image.jpg
-</code></td></tr></table>
-<blockquote>
-This example demonstrates the priorities of directory names specified using
-different techniques.  The output directory is taken from the first directory
-specified from the following list:  1) the <b>Directory</b> tag, 2) the
-directory part of the <b>FileName</b> tag, 3) the directory part of the
-<code>-o</code> option, or 4) the source directory, in that order.  The order of
-the arguments on the command line is not significant.  In this example, the
-target file is copied (not moved, because the <code>-o</code> option was used)
-to '<code>dir1/image.jpg</code>'. </blockquote>
-<blockquote>Note that both the <b>FileName</b> tag and the <code>-o</code>
-option may be used without a directory specification, in which case the
-directory with the next highest priority is used.  Also note that if
-<code>-o</code> specifies a directory, then the directory name must end with a
-'<code>/</code>' or the directory must already exist, otherwise ExifTool will
-interpret the last part as a file name. (eg. '<code>-o images/test</code>'
-specifies the '<code>images</code>' directory unless the
-'<code>images/test</code>' directory already exists, while '<code>-o
-images/test/</code>' unabiguously specifies the '<code>images/test</code>'
-directory.)
-</blockquote>
-<a name="ex12"></a><table cellpadding=6>
-<tr><td valign='top'>12.</td><td bgcolor='#dddddd'><code class='blk'>
-exiftool -d %Y/%m "-directory&lt;filemodifydate" "-directory&lt;createdate" "-directory&lt;datetimeoriginal" .
-</code></td></tr></table>
-<blockquote>Move image files from the current directory (<code>.</code>) into a
-directory hierarcy based on year/month.  In this command the Directory tag is
-set from multiple other date/time tags.  ExifTool evaluates the command-line
-arguments left to right, and latter assignments to the same tag override earlier
-ones, so the Directory for each image is ultimately set by the rightmost copy
-argument that is valid for that image.  Specifically, Directory is set from
-DateTimeOriginal if it exists, otherwise CreateDate if it exists, and finally
-FileModifyDate (which always exists) is used as a fallback.</blockquote>
-<a name="codes"></a><h2>Common Date Format Codes</h2>
-<p>Date format codes are used in the argument to the <code>-d</code> option to
-represent components of the date/time string.  The codes listed below are common
-to most systems, but additional codes may be available on your specific system
--- see your <i>strftime</i> man page for details.</p>
-<blockquote><table>
-<tr><th>%a</th><td>- abbreviated locale weekday name</td></tr>
-<tr><th>%A</th><td>- full locale weekday name</td></tr>
-<tr><th>%b</th><td>- abbreviated locale month name</td></tr>
-<tr><th>%B</th><td>- full locale month name</td></tr>
-<tr><th>%c</th><td>- preferred locale date/time representation</td></tr>
-<tr><th>%d</th><td>- day of month (01-31)</td></tr>
-<tr><th>%H</th><td>- hour on a 24-hour clock (00-23)</td></tr>
-<tr><th>%I</th><td>- hour on a 12-hour clock (01-12)</td></tr>
-<tr><th>%j</th><td>- day of year (001-366)</td></tr>
-<tr><th>%m</th><td>- month number (01-12)</td></tr>
-<tr><th>%M</th><td>- minute (00-59)</td></tr>
-<tr><th>%p</th><td>- 'AM' or 'PM'</td></tr>
-<tr><th>%s</th><td>- number of seconds since the Epoch, UTC (see note 1 below)</td></tr>
-<tr><th>%S</th><td>- seconds (00-59)</td></tr>
-<tr><th>%w</th><td>- weekday number (0-6)</td></tr>
-<tr><th>%W</th><td>- week number of the year (00-53)</td></tr>
-<tr><th>%x</th><td>- preferred locale date representation</td></tr>
-<tr><th>%X</th><td>- preferred locale time representation</td></tr>
-<tr><th>%y</th><td>- 2-digit year (00-99)</td></tr>
-<tr><th>%Y</th><td>- 4-digit year (eg. 2006)</td></tr>
-<tr><th>%z</th><td>- time zone in the form +/-hhmm (see note 1 below)</td></tr>
-<tr><th>%Z</th><td>- system time zone name (see note 2 below)</td></tr>
-<tr><th>%%</th><td>- a literal '%' character</td></tr>
-</table></blockquote>
-<p>ExifTool file name format codes may be used inside a date format
-string when a date/time tag is used to set the value of the <b>FileName</b> or
-<b>Directory</b> tags via the command-line interface.  In this case, an extra
-'<code>%</code>' must be added to pass the format code through the date/time
-parser:</p>
-<blockquote><table>
-<tr><th>%%d</th><td>- original file directory (including trailing "/" if necessary)</td></tr>
-<tr><th>%%f</th><td>- original file name (without the extension)</td></tr>
-<tr><th>%%e</th><td>- original file extension (not including the ".")</td></tr>
-<tr><th>%%c</th><td>- copy number (output files only)</td></tr>
-</table></blockquote>
-<p>See the <code>-w</code> option in the <a href="exiftool_pod.html">exiftool
-application documentation</a> for details about special features available
-with these name format codes.</p>
-<p><b>Notes:</b></p>
-<ol>
-<li>The %s and %z format codes use the time zone specified by the date/time
-value.  If the date/time value does not include a time zone specification, then
-it is interpreted as a local time in the system time zone.  These format codes
-are parsed by ExifTool, so they should work on all systems.<br><br></li>
-<li>The %Z format code ignores any time zone specified in the date/time value,
-and returns the system time-zone name for the given date/time interpreted as a
-local system time.</li>
-</ol>
-<hr>
-<p class='lf'><a href="index.html">&lt;-- Back to ExifTool home page</a></p>
-</body>
-</html>

data/bin/Image-ExifTool-10.04/html/geotag.html DELETED Viewed

@@ -1,654 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-        "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
-<html>
-<head>
-  <title>Geotagging with ExifTool</title>
-<link rel=stylesheet type='text/css' href='style.css' title='Style'>
-<style type="text/css">
-<!--
-pre  { color: #800; margin-left: 4em }
-.nr  { white-space: nowrap }
--->
-</style>
-</head>
-<body>
-<div class='index'>
-<a href="#Implementation">Implementation</a>
-<br>&nbsp; - <a href="#geotag">Geotag</a>
-<br>&nbsp; - <a href="#geosync">Geosync</a>
-<br>&nbsp; - <a href="#geotime">Geotime</a>
-<br><a href="#Examples">Examples</a>
-<br><a href="#Options">Options</a>
-<br><a href="#Orient">Orientation</a>
-<br><a href="#Troubleshooting">Troubleshooting</a>
-<br><a href="#Tips">Tips</a>
-<hr>
-<a href="#Inverse">Inverse Geotagging</a>
-<br>&nbsp; - <a href="#GPX">Creating GPX log</a>
-<br>&nbsp; - <a href="#KML">Creating KML file</a>
-</div>
-<h1 class='up'>Geotagging with ExifTool</h1>
-<p>The ExifTool geotagging feature adds GPS tags to images based on data from a
-GPS track log file.  The GPS track log file is loaded, and linear interpolation
-is used to determine the GPS position at the time of the image, then the
-following tags are written to the image (if the corresponding information
-is available):</p>
-<pre>GPSLatitude      GPSLongitude      GPSAltitude          GPSDateStamp
-GPSLatitudeRef   GPSLongitudeRef   GPSAltitudeRef       GPSTimeStamp
-GPSTrack         GPSSpeed          GPSImgDirection      GPSPitch
-GPSTrackRef      GPSSpeedRef       GPSImgDirectionRef   GPSRoll
-</pre>
-<blockquote class=lt><i>Note: GPSPitch and GPSRoll are not standard tags, and
-must be <a href="#Orient">user-defined</a>.</i></blockquote>
-<p>Currently supported GPS track log file formats:</p>
-<ul>
-<li>GPX</li>
-<li>NMEA (RMC, GGA, GLL and GSA sentences)</li>
-<li>KML</li>
-<li>IGC (glider format)</li>
-<li>Garmin XML and TCX</li>
-<li>Magellan eXplorist PMGNTRK</li>
-<li>Honeywell PTNTHPR (see <a href="#Orient">Orientation</a>)</li>
-<li>Bramor gEO log</li>
-<li>Winplus Beacon .TXT</li>
-</ul>
-<a name="Implementation"></a>
-<h3>Implementation</h3>
-<p>Geotagging is accomplished in ExifTool through the use of three special
-<a href="TagNames/Extra.html">Extra tags</a>:
-<code>Geotag</code>, <code>Geosync</code> and <code>Geotime</code>.</p>
-<blockquote class=lt><i>Note: When writing these tags, order is important. If
-<code>Geotime</code> is written, it must be done after both <code>Geotag</code>
-and <code>Geosync</code>.</i></blockquote>
-<a name="geotag"></a>
-<h4>Geotag</h4>
-<p>The <code>Geotag</code> tag is used to define the GPS track log data. The
-geotagging feature is activated by assigning the name of a track log file to
-this tag.  As an example, the following command line adds GPS tags to all images
-in the "/Users/Phil/Pictures" directory based on GPS positions stored in the
-track log file "track.log" in the current directory:</p>
-<pre>exiftool -geotag=track.log /Users/Phil/Pictures
-</pre>
-<p>As a convienience the exiftool application also provides a
-<code>-geotag</code> option, so the following command is equivalent to the one
-above:</p>
-<pre>exiftool -geotag track.log /Users/Phil/Pictures
-</pre>
-<p>Multiple GPS log files may be loaded simultaneously by using more than one
-<code>-geotag</code> option or <code>-geotag=</code> assignment in the same
-command.  This allows batch processing of images spanning different tracks with
-a single command.  Wildcards may be used in the argument of the
-<code>-geotag</code> option, but note that the argument may then need to be
-quoted on some systems to prevent shell globbing, and that wildcards are not
-supported with the <code>-geotag=</code> syntax.  See the
-<a href="#Examples">examples</a> below.</p>
-<p>Deleting the <code>Geotag</code> tag (with <code>-geotag=</code>) causes the
-GPS tags written by the <code>-geotag</code> feature to be deleted.</p>
-<blockquote class=lt><i>Programmers:  You may write either a GPS log file name
-or the GPS log data as the value for <code>Geotag</code>.  If the value contains
-a newline or a null byte it is assumed to be data, otherwise it is taken as a
-file name.</i></blockquote>
-<a name="geosync"></a>
-<h4>Geosync</h4>
-<p>The <code>Geosync</code> tag is needed only when the image timestamps are not
-properly synchronized with GPS time, and must be set before <code>Geotime</code>
-to be effective.  The value written to the <code>Geosync</code> tag may take a
-number of different forms, but the basic format is that of a simple time
-difference which is added to <code>Geotime</code> before interpolating the GPS
-position in the track log.  This time difference may be of the form "SS",
-"MM:SS", "HH:MM:SS" or "DD HH:MM:SS" (where SS=seconds, MM=minutes, HH=hours and
-DD=days), and a leading "+" or "-" may be added for positive or negative
-differences (negative if the camera clock was ahead of GPS time).  Fractional
-seconds are allowed (eg. "SS.ss").</p>
-<p>For example, "<code>-geosync=-1:20</code>" specifies that synchronization
-with GPS time is achieved by subtracting 1 minute and 20 seconds from the
-<code>Geotime</code> value.  See the <a href="#TP1">Time Synchronization Tip</a>
-below for more details.</p>
-<blockquote class=lt><i>Note that a single decimal value is interpreted as
-seconds when written to <code>Geosync</code>.  This is different from of other
-date/time shift values where a single value is normally taken as hours.</i>
-</blockquote>
-<p>The <code>Geosync</code> value may also be specified using 3 different
-formats which provide a GPS time and a corresponding camera clock time.  While
-these formats may be used for a simple (constant) time synchronization offset,
-they are necessary when performing a clock drift correction (with multiple
-synchronization points), and are described below.</p>
-<p><b>Camera clock drift correction:</b></p>
-<p>A more advanced <code>Geosync</code> feature allows the GPS time and the
-image time to be specified together, facilitating a time drift correction if
-more than one synchronization point is provided.  For this, the value written to
-<code>Geosync</code> takes one of the following forms:</p>
-<blockquote>
-<table class='norm'>
-<tr><th>Format</th><th>Notes</th></tr>
-<tr><td><i>FILE</i></td>
-<td>Both GPS and image timestamps are extracted from the
-specified file. eg) <code>-geosync=image.jpg</code></td></tr>
-<tr><td><i>GPSTIME</i>@<i>FILE</i></td><td>GPS time is taken from the
-<code>Geosync</code> value and the image timestamp is extracted from the
-specified file. eg) <code>-geosync="12:58:05@image.jpg"</code></td></tr>
-<tr><td><i>GPSTIME</i>@<i>IMGTIME</i></td><td>Both GPS and image timestamps are
-taken from the <code>Geosync</code> value.  eg)
-<code>-geosync="12:58:05@2010:01:02 12:25:26"</code></td></tr>
-</table></blockquote>
-<p>The values of <i>GPSTIME</i> and <i>IMGTIME</i> specified on the command line
-may contain a date, but it is not necessary.</p>
-<p>Notes:</p>
-<ol>
-<li>If either the GPS or the image timestamp does not contain a date, the two
-timestamps are assumed to be on days which place them within 12 hours of each
-other.</li>
-<li>If neither the GPS nor the image timestamps contain a date, this
-synchronization point may only be used for constant time offset (ie. no time
-drift correction will be applied).</li>
-<li>Both the GPS and the image times are assumed to be local unless another
-timezone is specified.</li>
-<li>Both the GPS and the image time values may contain decimal seconds.</li>
-<li>The applied value of the time drift correction is calculated from a
-piecewise linear interpolation/extrapolation between the synchronization points
-if more than one <code>Geosync</code> value is defined.</li>
-<li>When extracting from file, timestamps are taken from the first available of
-the following tags:
-<ul>
-<li>Image timestamp: SubSecDateTimeOriginal, SubSecCreateDate, SubSecModifyDate,
-DateTimeOriginal, CreateDate, ModifyDate, FileModifyDate</li>
-<li>GPS timestamp: GPSDateTime, GPSTimeStamp</li>
-</ul></li>
-</ol>
-<a name="geotime"></a>
-<h4>Geotime</h4>
-<p>The <code>Geotime</code> tag specifies the point in time for which the GPS
-position is calculated (by interpolating between fixes in the GPS track log).
-Unless a group is specified, exiftool writes the generated tags to the default
-groups.  If a value for <code>Geotime</code> is not given, it is taken from
-<code>DateTimeOriginal</code> for each image (as if
-<code>"-Geotime&lt;DateTimeOriginal"</code> had been specified), but the value
-may be copied from any other date/time tag or set directly from a date/time
-string.</p>
-<p>If the date/time tag does not include a timezone then one may be added (eg.
-<code>"-Geotime&lt;${CreateDate}-05:00"</code>), otherwise the local system time
-is assumed.  Decimal seconds are supported in the time value.</p>
-<p>By default, GPS tags are created in EXIF and the corresponding
-XMP tags are updated only if they already exist.  However, an EXIF or XMP group
-name may be specified to force writing only to the specified location.  For
-example, writing <code>XMP:Geotime</code> or <code>EXIF:Geotime</code> will
-write the generated GPS tags only to XMP or EXIF respectively.  Note that when
-written to XMP, the <code>GPSLatitudeRef</code> and <code>GPSLongitudeRef</code>
-tags are not used, and the XMP <code>GPSDateTime</code> tag is written instead
-of the separate EXIF <code>GPSDateStamp</code> and <code>GPSTimeStamp</code>
-tags.</p>
-<p>See the <a href="#Examples">Examples</a> section below for sample command
-lines illustrating various aspects of the geotagging feature.</p>
-<blockquote class=lt><i>Programmers:  Note that <code>Geotime</code> must always
-be specified when geotagging via the API -- the default value of
-<code>DateTimeOriginal</code> is implemented by the application.</i>
-</blockquote>
-<a name="Examples"></a>
-<h3>Examples</h3>
-<p>Geotag all images in the "c:\images" directory from position information in a
-GPS track log ("c:\gps logs\track.log").  Since the <code>Geotime</code> time is
-not specified, the value of <code>DateTimeOriginal</code> is used.  Local system
-time is assumed unless <code>DateTimeOriginal</code> contains a timezone:</p>
-<pre>exiftool -geotag "c:\gps logs\track.log" c:\images</pre>
-<p>Geotag all images in directory "dir" from the GPS positions in "track.log"
-(in the current directory), for a camera clock that was running 25 seconds
-slower than the GPS clock:</p>
-<pre>exiftool -geotag track.log -geosync=+25 dir</pre>
-<p>Geotag an image with the GPS position for a specific time.  (Note that the
-<code>Geotag</code> tag must be assigned before <code>Geotime</code> for the GPS
-data to be available when <code>Geotime</code> is set):</p>
-<pre>exiftool -geotag t.log -geotime="2009:04:02 13:41:12-05:00" a.jpg</pre>
-<p>Geotag all images in directory "dir" with XMP tags instead of EXIF tags,
-based on the image <code>CreateDate</code>.  (In this case, the order of the
-arguments doesn't matter because tags with values copied from other tags are
-always set after constant values):</p>
-<pre>exiftool -geotag log.gpx "-xmp:geotime&lt;createdate" dir</pre>
-<p>Geotag images in "dir" using <code>CreateDate</code> with the specified
-timezone.  If <code>CreateDate</code> already contained a timezone, then the
-timezone specified on the command line is ignored.  (Note that in Windows,
-double quotes (<code>"</code>) must be used instead of single quotes
-(<code>'</code>) around the <code>-geotime</code> argument in the next 2
-commands):</p>
-<pre>exiftool -geotag a.log '-geotime&lt;${createdate}+01:00' dir</pre>
-<p>Geotag images for which the camera clock was set to UTC (+00:00), using
-the time from <code>DateTimeOriginal</code>:</p>
-<pre>exiftool -geotag trk.gpx '-geotime&lt;${DateTimeOriginal}+00:00' dir</pre>
-<p>Delete GPS tags which were added by the geotag feature. (Note that this does
-not remove all GPS tags -- to do this instead use <code>-gps:all=</code>):</p>
-<pre>exiftool -geotag= a.jpg</pre>
-<p>Delete XMP GPS tags which were added by the geotag feature:</p>
-<pre>exiftool -xmp:geotag= a.jpg</pre>
-<p>Geotag an image with XMP tags, using the time from
-<code>DateTimeOriginal</code>:</p>
-<pre>exiftool -xmp:geotag=track.log a.jpg</pre>
-<p>Combine multiple track logs and geotag an entire directory tree of
-images:</p>
-<pre>exiftool -geotag a.log -geotag b.log -r dir</pre>
-<p>Use wildcards to load multiple track files (the quotes are necessary for most
-operating systems to prevent filename expansion):</p>
-<pre>exiftool -geotag "logs/*.log" dir</pre>
-<p>Geotag from a sub-second date/time value with a sub-second time synchronization
-(only possible if the EXIF sub-second time stamps are available):</p>
-<pre>exiftool -Geotag a.log -Geosync=+13.42 "-Geotime&lt;SubSecDateTimeOriginal" dir
-</pre>
-<p>Geotag images with a piecewise linear time drift correction using the GPS
-time synchronization from three already-geotagged images:</p>
-<pre>exiftool -geotag a.log -geosync=1.jpg -geosync=2.jpg -geosync=3.jpg dir
-</pre>
-<a name="Options"></a>
-<h3>Options</h3>
-<p>Geotagging may be configured via the following ExifTool options.  These
-options may be set using either the <code>-api</code> option of the command-line
-application, the Options() function of the API, or the
-%Image::ExifTool::UserDefined::Options hash of the config file.  (See the
-<a href="config.html">sample config file</a> for details about how to use the
-config file.)</p>
-<blockquote>
-<table class='norm'>
-<tr><th>Option</th><th>Description</th><th>Values</th><th>Default</th></tr>
-<tr><td>GeoMaxIntSecs</td>
-    <td>Maximum interpolation time in seconds for geotagging.  Geotagging is
-    treated as an extrapolation if the Geotime value lies between two fixes in
-    the same track which are separated by a number of seconds greater than this.
-     Otherwise, the coordinates are calculated as a linear interpolation between
-    the nearest fixes on either side of the Geotime value.  Set to 0 to disable
-    interpolation and use the coordinates of the nearest fix instead (provided
-    it is within GeoMaxExtSecs, otherwise geotagging fails).</td>
-    <td align='center'>A&nbsp;floating&nbsp;point&nbsp;number</td>
-    <td align='center'>1800</td></tr>
-<tr><td>GeoMaxExtSecs</td>
-    <td>Maximum extrapolation time in seconds for geotagging.  Geotagging fails
-    if the Geotime value lies outside a GPS track by a number of seconds greater
-    than this.  Otherwise, the coordinates of the nearest fix are taken.</td>
-    <td align='center'>A&nbsp;floating&nbsp;point&nbsp;number</td>
-    <td align='center'>1800</td></tr>
-<tr><td>GeoMaxHDOP</td>
-    <td>Maximum Horizontal (2D) Dilution Of Precision for geotagging.  GPS fixes are
-    ignored if the HDOP is greater than this.</td>
-    <td align='center'>A&nbsp;floating&nbsp;point&nbsp;number, or undef to disable</td>
-    <td align='center'>undef</td></tr>
-<tr><td>GeoMaxPDOP</td>
-    <td>Maximum Position (3D) Dilution Of Precision for geotagging.  GPS fixes are
-    ignored if the PDOP is greater than this.</td>
-    <td align='center'>A&nbsp;floating&nbsp;point&nbsp;number, or undef to disable</td>
-    <td align='center'>undef</td></tr>
-<tr><td>GeoMinSats</td>
-    <td>Minimum number of satellites for geotagging.  GPS fixes are ignored if the
-    number of acquired satellites is less than this.</td>
-    <td align='center'>A positive integer, or undef to disable</td>
-    <td align='center'>undef</td></tr>
-</table></blockquote>
-<a name="Orient"></a>
-<h3>Orientation</h3>
-<p>ExifTool reads orientation information from the PTNTHPR sentence generated by
-some Honeywell digital compasses. This is a proprietary NMEA sentence which
-contains information about heading, pitch and roll angles.  When this
-information is available, the heading is written to GPSImgDirection (and
-GPSImgDirectionRef is set to "T"), but no standard GPS tags exist for pitch and
-roll.  Regardless, ExifTool attempts to write GPSPitch and GPSRoll tags. For
-this information to be stored, appropriate user-defined tags must be created.
-Below is a simple config file which defines the necessary EXIF GPS tags.
-Corresponding XMP-exif tags may also be created. See the
-<a href="config.html">config file documentation</a> for more information.</p>
-<pre>%Image::ExifTool::UserDefined = (
-    'Image::ExifTool::GPS::Main' => {
-        0xd000 => {
-            Name => 'GPSPitch',
-            Writable => 'rational64s',
-        },
-        0xd001 => {
-            Name => 'GPSRoll',
-            Writable => 'rational64s',
-        },
-    },
-);
-1; #end
-</pre>
-<a name="Troubleshooting"></a>
-<h3>Troubleshooting</h3>
-<a name="TR1"></a>
-<p>1. <b>"No track points found in GPS file"</b></p>
-<blockquote>If you see the above message, either exiftool does not yet support
-your track log file format, or your track log does not contain the necessary
-position/timestamp information.  For instance, in KML files each Placemark must
-contain a TimeStamp.  If you believe your track log contains the necessary
-information, please send me a sample file and I will add support for this
-format.</blockquote>
-<a name="TR2"></a>
-<p>2. <b>"0 image files updated"</b></p>
-<blockquote>If you see this message without any other warning messages, it is
-likely that <code>Geotime</code> didn't get set properly.</blockquote>
-<blockquote>Be sure that the necessary date/time tag exists in your image for
-copying to <code>Geotime</code>.  Unless otherwise specified, the required tag
-is <code>DateTimeOriginal</code>.  The following command may be used to list the
-names and values of all available date/time tags in an image:
-<pre>exiftool -s -time:all image.jpg
-</pre>
-Even if there is no metadata in the image you may be able to set
-<code>Geotime</code> from the filesystem modification date for the image (which
-will appear as <code>FileModifyDate</code> in the output of the above command).
-In this case you may also want to include the <code>-P</code> option to preserve
-the original value of <code>FileModifyDate</code>:
-<pre>exiftool -geotag track.gpx "-geotime&lt;filemodifydate" -P image.jpg
-</pre>
-Without the <code>-P</code> option, <code>FileModifyDate</code> is set to the
-current date/time when the file is rewritten.</blockquote>
-<a name="TR3"></a>
-<p>3. <b>"Warning: Time is too far before track in File:Geotime (ValueConvInv)"</b></p>
-<blockquote>If you see a warning like this, you may have a time zone problem,
-or a time synchronization issue.  Keep in mind that GPS times are in UTC, but
-the camera times are typically in your local time zone.</blockquote>
-<blockquote>To see more details about what ExifTool is doing, try adding the
-<code>-v2</code> option to your command.  You should then see messages like
-this if the GPS track log was loaded successfully:
-<pre>Loaded 372 points from GPS track log file 'my_track.log'
-  GPS track start: 2009:03:30 19:45:25 UTC
-  GPS track end:   2009:04:03 11:16:04 UTC
-</pre>
-If the number of points loaded and start/end times seem reasonable, then
-the problem is likely in the time synchronization.  Also printed will be the
-UTC time for the image:
-<pre>  Geotime value:   2009:04:03 10:57:01 UTC (local timezone is -05:00)
-</pre>
-The "Geotime value" must lie within 1/2 hour of a valid GPS fix in the track log
-for a position to be calculated. (1/2 hour is the default, but this can be
-configured via the geotagging <a href="#Options">Options</a>.)  The time
-calibration relies on proper synchronization between the GPS time and your
-camera's clock.  If a timezone is not specified, the local system time zone (as
-set by the shell's TZ environment variable) is printed in the above message and
-used to convert the <code>Geotime</code> value to UTC.  You should specify the
-timezone for <code>Geotime</code> if your images were taken in a different
-timezone (see <a href="#Examples">Examples</a> above).  If the camera clock was
-wrong, the <code>Geosync</code> tag may be used to apply a time correction, or
-the ExifTool time shift feature may be used to adjust the image times before
-geotagging -- see the <a href="#TP1">Time Synchronization</a> tip below for
-examples.</blockquote>
-<a name="Tips"></a>
-<h3>Tips</h3>
-<a name="TP1"></a>
-<p>1. <b>Time Synchronization</b></p>
-<blockquote>One way to accurately synchronize your images with GPS time is to
-take a picture of the time displayed on your GPS unit while you are out
-shooting.  Then after you download your images you can use this image to
-synchronize the image timestamps for geotagging.  This is done by using an image
-viewer to read the time from the GPS display in the image, and exiftool to
-extract <code>DateTimeOriginal</code> from the file. For example, if the time in
-the GPS display reads 19:32:21 UTC and <code>DateTimeOriginal</code> is
-14:31:49, then for this image the camera clock was 32 seconds slow (assuming
-that the timezone of the camera clock was <span class=nr>-05:00</span>). There
-are two different ways to use this time synchronization to improve your
-geotagging accuracy:
-</blockquote>
-<blockquote>A) Use the <code>Geosync</code> tag to specify the time difference
-while geotagging.  Using this technique the existing image timestamps will not
-be corrected, but the <code>GPSTimeStamp</code> tag created by the geotagging
-process will contain the correct GPS time:
-<pre>exiftool -geosync=+00:00:32 -geotag my_gps.log C:\Images
-</pre>
-or equivalently,
-<pre>exiftool -geosync=19:32:21Z@14:31:49-05:00 -geotag my_gps.log C:\Images
-</pre>
-<i class=lt>(Note that this technique may also be used for a more advanced time
-drift correction.  See the <a href='#geosync'>Geosync section above</a> for
-details)</i></blockquote>
-<blockquote>B) First fix the image timestamps by shifting them to synchronize
-with GPS time, then geotag using the corrected timestamps:
-<pre>exiftool -alldates+=00:00:32 C:\Images
-exiftool -geotag my_gps.log C:\Images
-</pre>
-Both examples above assume that your track log file (<code>my_gps.log</code>)
-is in the current directory, that the images were downloaded to the
-<code>C:\Images</code> directory, and that the computer and camera clocks are
-in the same timezone.</blockquote>
-<hr>
-<a name="Inverse"></a>
-<h2>Inverse Geotagging</h2>
-<p>The <code>-p</code> option may be used to output files in any number of formats.
-This section gives examples for creating GPX and KML output files from a set of
-geotagged images, or from a geotagged video file.  (But note that the
-<code>-ee</code> option must be added to the commands below to extract the full
-track from a video file, and currently only M2TS videos are supported for this
-feature.)</p>
-<a name="GPX"></a>
-<h4>Creating a GPX track log</h4>
-<p>The following print format file may be used to generate a GPX track log from
-one or more geotagged images:</p>
-<pre>#------------------------------------------------------------------------------
-# File:         gpx.fmt
-#
-# Description:  Example ExifTool print format file for generating GPX track log
-#
-# Usage:        exiftool -p gpx.fmt -d %Y-%m-%dT%H:%M:%SZ FILE [...] > out.gpx
-#
-# Requires:     ExifTool version 8.10 or later
-#
-# Revisions:    2010/02/05 - P. Harvey created
-#
-# Notes:     1) All input files must contain GPSLatitude and GPSLongitude.
-#            2) The -fileOrder option may be used to control the order of the
-#               generated track points.
-#------------------------------------------------------------------------------
-#[HEAD]&lt;?xml version="1.0" encoding="utf-8"?&gt;
-#[HEAD]&lt;gpx version="1.0"
-#[HEAD] creator="ExifTool $ExifToolVersion"
-#[HEAD] xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-#[HEAD] xmlns="http://www.topografix.com/GPX/1/0"
-#[HEAD] xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd"&gt;
-#[HEAD]&lt;trk&gt;
-#[HEAD]&lt;number&gt;1&lt;/number&gt;
-#[HEAD]&lt;trkseg&gt;
-#[BODY]&lt;trkpt lat="$gpslatitude#" lon="$gpslongitude#"&gt;
-#[BODY]  &lt;ele&gt;$gpsaltitude#&lt;/ele&gt;
-#[BODY]  &lt;time&gt;$gpsdatetime&lt;/time&gt;
-#[BODY]&lt;/trkpt&gt;
-#[TAIL]&lt;/trkseg&gt;
-#[TAIL]&lt;/trk&gt;
-#[TAIL]&lt;/gpx&gt;
-</pre>
-<p>This example assumes that the <code>GPSLatitude</code>,
-<code>GPSLongitude</code>, <code>GPSAltitude</code> and <code>GPSDateTime</code>
-tags are all available in each processed <i>FILE</i>.  Warnings will be
-generated for missing tags.  The output GPX format will invalid if any
-<code>GPSLatitude</code> or <code>GPSLongitude</code> tags are missing, but will
-be OK for missing <code>GPSAltitude</code> or <code>GPSDateTime</code> tags.</p>
-<p>Note that the order of track points in the output GPX file will be the same
-as the order of processing the input files, which may not be chronological
-depending on how the files are named.  The <code>-fileOrder</code> option may be
-used to force processing of files in a particular order.  For example, the
-following command processes files in order of increasing <code>GPSDateTime</code>:
-</p>
-<pre>exiftool -fileOrder gpsdatetime -p gpx.fmt -d %Y-%m-%dT%H:%M:%SZ /Users/Phil/Pictures > out.gpx
-</pre>
-<p>Since no directory was specified for <code>gpx.fmt</code>, this file must
-exist in the current directory when the above command is executed. (If the
-<code>gpx.fmt</code> file can't be found then the <code>-p</code> argument is
-interpreted as a string instead of a file name, and the text
-"<code>gpx.fmt</code>" is sent to the output, which isn't what we want.)</p>
-<p>The <code>-if</code> option may be added to ensure that only files containing
-GPS information are processed.  For example, the following command creates
-"<code>out.gpx</code>" in the current directory from all pictures containing
-<code>GPSDateTime</code> information in directory "<code>pics</code>" and its
-sub-directories:</p>
-<pre>exiftool -r -if '$gpsdatetime' -fileOrder gpsdatetime -p gpx.fmt -d %Y-%m-%dT%H:%M:%SZ pics > out.gpx
-</pre>
-<p>Note:  In Windows, double quotes (<code>"</code>) must be used instead of
-single quotes (<code>'</code>) around the <code>-if</code> argument above.</p>
-<p>The "fmt_files" directory of the full exiftool distribution contains this
-sample format file ("gpx.fmt") as well as a sample which creates GPX waypoints
-with pictures ("gpx_wpt.fmt").</p>
-<a name="KML"></a>
-<h4>Creating a Google Earth KML file</h4>
-<p>Below is an example of a print format file which generates a Google Earth KML
-file from a collection of geotagged images:</p>
-<pre>#------------------------------------------------------------------------------
-# File:         kml.fmt
-#
-# Description:  Example ExifTool print format file for generating a
-#               Google Earth KML file from a collection of geotagged images
-#
-# Usage:        exiftool -p kml.fmt FILE [...] > out.kml
-#
-# Requires:     ExifTool version 8.10 or later
-#
-# Revisions:    2010/02/05 - P. Harvey created
-#               2013/02/05 - PH Fixed camera icon to work with new Google Earth
-#
-# Notes:     1) All input files must contain GPSLatitude and GPSLongitude.
-#            2) For Google Earth to be able to find the images, the input
-#               images must be specified using relative paths, and "out.kml"
-#               must stay in the same directory as where the command was run.
-#            3) Google Earth is picky about the case of the image file extension,
-#               and may not be able to display the image if an upper-case
-#               extension is used.
-#            4) The -fileOrder option may be used to control the order of the
-#               generated placemarks.
-#------------------------------------------------------------------------------
-#[HEAD]&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-#[HEAD]&lt;kml xmlns="http://earth.google.com/kml/2.0"&gt;
-#[HEAD]  &lt;Document&gt;
-#[HEAD]    &lt;name&gt;My Photos&lt;/name&gt;
-#[HEAD]    &lt;open&gt;1&lt;/open&gt;
-#[HEAD]    &lt;Style id="Photo"&gt;
-#[HEAD]      &lt;IconStyle&gt;
-#[HEAD]        &lt;Icon&gt;
-#[HEAD]          &lt;href&gt;http://maps.google.com/mapfiles/kml/pal4/icon38.png&lt;/href&gt;
-#[HEAD]          &lt;scale&gt;1.0&lt;/scale&gt;
-#[HEAD]        &lt;/Icon&gt;
-#[HEAD]      &lt;/IconStyle&gt;
-#[HEAD]    &lt;/Style&gt;
-#[HEAD]    &lt;Folder&gt;
-#[HEAD]      &lt;name&gt;Waypoints&lt;/name&gt;
-#[HEAD]      &lt;open&gt;0&lt;/open&gt;
-#[BODY]      &lt;Placemark&gt;
-#[BODY]        &lt;description&gt;&lt;![CDATA[&lt;br/&gt;&lt;table&gt;&lt;tr&gt;&lt;td&gt;
-#[BODY]        &lt;img src='$directory/$filename'
-#[BODY]          width='$imagewidth' height='$imageheight'&gt;
-#[BODY]        &lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;]]&gt;&lt;/description&gt;
-#[BODY]        &lt;Snippet/&gt;
-#[BODY]        &lt;name&gt;$filename&lt;/name&gt;
-#[BODY]        &lt;styleUrl&gt;#Photo&lt;/styleUrl&gt;
-#[BODY]        &lt;Point&gt;
-#[BODY]          &lt;altitudeMode&gt;clampedToGround&lt;/altitudeMode&gt;
-#[BODY]          &lt;coordinates&gt;$gpslongitude#,$gpslatitude#,0&lt;/coordinates&gt;
-#[BODY]        &lt;/Point&gt;
-#[BODY]      &lt;/Placemark&gt;
-#[TAIL]    &lt;/Folder&gt;
-#[TAIL]  &lt;/Document&gt;
-#[TAIL]&lt;/kml&gt;
-</pre>
-<p>This example print format file is included in the "fmt_files" directory of
-the full ExifTool distribution.</p>
-<hr>
-<i>Created Apr. 2, 2009</i><br>
-<i>Last revised Mar. 5, 2015</i>
-<p class='lf'><a href="index.html">&lt;-- Back to ExifTool home page</a></p>
-</body>
-</html>