To batch process a collection of photo meta data, invoke createPhotoGalleryPages with the desired arguments.
This will process all *.photo_metdata and *.video_metadata files in the directory specified by the PHOTO_META_DIR environment variable. The meta data files will first be passed over using runSedScripts with alterImagePaths.sed and wordSubstitutes.sed. Alter these as needed. The available latitude and longitude data is extracted and the images are sorted in an attempt to group photos of a particular area together.
A pass is made over each known region name and generatePagesFromPhotoMetaData is invoked with the sorted subset of images for that region.
As a final step, it loops over the regions of interest and uses generateRegionPage to create a top-level region page for each distinct region and a world map as globe.html.
A potentially more useful sample usage, which assumes:
is realized by the following command invocation:
createPhotoGalleryPages ‑‑regen ‑‑makethumbnails ‑‑downsize 800 ‑‑makelinks ‑‑copydir `pwd`/images ‑‑droproot `pwd`/
A more complicated setup is illustrated by the scenario of having content from different trips stored in distinct directories. The PHOTO_PATHS variable is set to point at the various trip directories.
Raw images that have been post-processed for color-correction and dust removal are stored in a common BestOf directory and the OVERRIDE_PHOTO_PATHS variable is set to its location.
# NOTE: source this file
# set environment for photo gallery generation
PHOTO_META_DIR=`pwd`/metaDataFiles
export PHOTO_META_DIR
PHOTO_PATHS="/NASmount/pictures/Trip_2018"
PHOTO_PATHS="${PHOTO_PATHS} /NASmount/pictures/Trip_2017"
PHOTO_PATHS="${PHOTO_PATHS} /NASmount/pictures/Trip_2016"
PHOTO_PATHS="${PHOTO_PATHS} /NASmount/pictures"
export PHOTO_PATHS
OVERRIDE_PHOTO_PATHS="/NASmount/pictures/BestOf"
export OVERRIDE_PHOTO_PATHS
DEFAULT_REGION_LINKS="AUTO"
export DEFAULT_REGION_LINKS
ROOT_PAGE_HTML="/myHomePage.html"
ROOT_PAGE_LABEL="My Home Page"
export ROOT_PAGE_HTML
export ROOT_PAGE_LABEL
With these environment variables set, all of the content is processed via:
createPhotoGalleryPages ‑‑regen ‑‑downsize 752 ‑‑copydir `pwd`/MyTrips/images ‑‑makethumbnails ‑‑makelinks ‑‑droproot `pwd`/ -v ‑‑addroot /MyTrips
Top-level generation of individual photo-and-map pages:
generatePagesFromPhotoMetaData *.photo_metadata
which is a trivial cover script that invokes generatePhotoPage.
The generatePhotoPage script does most of the work, as it updates the image database CSV file for subsequent use in creating a region map with generateRegionPage, creates thumbnails, copies or sets up symbolic links for a directory of prepared images, rotates images if needed and transcodes videos into the MP4 format.
The generatePhotoPage script invokes the script makeGalleryPageHTML to generate the actual HTML document that will display a single photograph or video and the associated detail map indicating where the imagery was obtained.
A top-level map of a region with markers is created by the script generateRegionPage using content from the image database CSV file. It uses the AWK script makeRegionPageHTML.awk to generate the HTML page for the region map.
The script getPhotoMetaData is used to retrieve data from the *.photo_metadata files, which are in a trivial XML-like format. This trivial format has the restriction that the begin and end tags must all begin on new lines and be the sole content of that line.
Templates of photo meta data can be generated by makePhotoMetaTemplate, but the actual content is expected to be populated by hand using a text editor.
Individual photo pages are named similar to: regionMaps/{regionName}/imageAndMap_XXXXXX.html
The top-level map for a region is named: regionMaps/{regionName}.html
Note: Spaces in a {regionName} are converted to underscores ("_").
The createPhotoGalleryPages script generates a master page of all regions as globe.html.
The ‑‑droproot option can be used to remove the initial part of an image path in the generated files, which is useful for removing absolute paths that reference the original filesystem locations. A common argument value is `pwd`/, which drops the path of the current working directory. Note the trailing "/".
The ‑‑addroot option can be used to add a prefix to all of the generated files, which is useful if one wants the content assembled in a subdirectory. If it begins with a "/", the generated links will be absolute; otherwise a relative link will be generated.
The A_HOOK_from_batch_to_shell.bat Windows batch script can be used as a drag-and-drop target in Microsoft Windows File Explorer. It will invoke a Bourne shell script, currently DO_intendedCmd_makePhotoMetaTemplate.runsh, which usually means cygwin needs to be installed. The batch script can be edited to invoke a different program if similar utility is useful elsewhere.
The DO_intendedCmd_makePhotoMetaTemplate gets the target invocation program from the final part of the filename. It can be copied or used as a hard link with alternate names to invoke different programs without requiring modification of the script. It is normally called from the A_HOOK_batch_to_shell.bat script as a result of a Windows File Explorer drag-and-drop operation.
The .photo_metadata/.video_metadata file format has a trivial XML-like syntax that has two restrictions:
Both of the two file suffixes are recognized and video-related metadata can be stored in a .photo_metadata file. It is a matter of personal preference as to whether the distinct file name suffixes are used depending on the type of the source content to be displayed.
<title> World Peace Gate at Seoul Olympic Park </title> <description> The World Peace Gate was built for the 1988 Olympics held in Seoul. </description> <image_source> pictures/Fixed_JapanSeoul2018/D7514154.JPG </image_source> <region> South Korea </region>
Note that content between the corresponding start and ending attribute tag may consist of multiple lines. The description content is often comprised of several lines of text.
These tags are currently recognized by createPhotoGalleryPages and generatePagesFromPhotoMetaData.
Additional user-defined tags can be used without breaking existing scripts.
The hierarchy of programs appears as illustrated below:
Questions can be sent to:
Geoff Carpenter http://www.fargos.net/gcc.html