Photo and Image Handling

Photo and Image Handling

Gigatrees includes special handling of profile photos for individuals as well as other images for sources, source references and events. Profile photos will be included on both the Photos page and on individual profile pages when the path to the photo is browsable. Other types of images are included on the source pages if they are defined or referenced by a source, and appear elsewhere otherwise. Details for photos and images are included on their tooltips. On the Photos page hover over an image to view the tooltips. Click on any of the links that appear in the tooltips to view the photo on the person's profile page, and click on any photo to view it using the FancyBox plugin that is loaded in the default Metadata Header.

Gigatrees recognizes several methods for defining photos and images along with vendor specific GEDCOM extensions for each.

Profile photos are defined by configuring a multimedia logical record (OBJE) and then referencing that record by an individual or family, or by defining an embedded multimedia record (OBJE) as part of an individual or family. When multimedia records are defined or referenced as part of a family, they will be included in the profile photos for the family's husband and wife only, not their children. Multimedia records support the GEDCOM tags: "FILE", "FILE.TITL" and "TITL". The file path can be set using either an absolute disk path, an absolute web path or a relative path. If the path does not end in a browsable photo extension ("png", "jpg", etc.) it will be interpreted as a URL instead.

Gigatrees supports several optional vendor specific mutlimedia record fields including:
_PHOTO - used instead of the "OBJE" when embedding photos or images
_FILE - used instead of the "FILE" field to include the path to the photo image
_TITL - used instead of the "TITL" field to include a photo title
_PIC - used to include the path to the thumbnail image if there is one
_CAP or _CMNT - used to include a caption
_SUBM - used to include submitter information
_NOTE - used instead of the "NOTE" field to include photo notes
_PLAC - used to include photo location information
_DATE - used to include photo date information.

The above tags can also be added to your GEDCOM file, or if you prefer, without modifying your GEDCOM file by using the Append Records option.

Source images can be defined using a multimedia record as described above or by using a "URL" tag with a path having an image browsable extension. Other types of extensions are treated as URLs. The vendor specific "_PIC" and "_TITL" fields are supported. The example shown uses relative paths.

0 @S1@ SOUR	
1 URL /folder/pics/1790-census-ny-ny-ny.png
2 _PIC /folder/pics/thumbs/1790-census-ny-ny-ny-thumb.png
2 _TITL 1790 U.S. Federal Census, New York City, New York, New York

In the above example, "WWW", "_URL", "_WEB", and "_LINK" tags can be used in place of the "URL" tag.

The _WEBTAG record is also supported for defining source images. Web tags use the "NAME" field for the image title, and the "URL" field as described above.

0 @S1@ SOUR
2 NAME Photo of my Uncle Walt
2 URL c:/folder/pics/walt.png
3 _PIC c:/folder/pics/thumbs/walt-thumb.png

The Images option includes three separate path fields, Profile Photos, Source Images and Thumbnails that can be configured. The strings you configure in these path fields will be prepended to paths found in your GEDCOM file. So for instance if you wanted to view the images containing an absolute disk path ( c: ) in an offline tree, you would add file:// to each of these path options. This would allow your absolute paths to be viewed in a browser. You will need to make sure that the Hide Local Links option is disabled under Security, it is enabled by default. If your GEDCOM file uses relative paths like "/folder/pics/walt.png", and they were included in an adjacent folder, for example, then you could add file://.. to the paths to make them viewable offline. If you were using relative paths and were viewing your images in an online tree, then could be used in the path options to remap them for viewing. If, on the otherhand, you need to remap absolute paths, then you would need to use the Replace Text option to strip your absolute path making your paths relative.

Depending on how unique the absolute paths in your GEDCOM file are, you may be able to leave the path options empty and do all the remapping using the Replace Text option. If you are publishing your tree online and cannot or do not want to remap your local photos, then you can enable the Hide Local Links option under Security to remove all absolute links to both photos and URLs. Relative paths will not be affected by this option. It may be best to use absolute paths in your GEDCOM file so that you can more easily decide later to either remap them or hide them.

When thumbnails are not provided, default images are used instead. The default images are located in the installation's assets folder. You can replace these if desired. Gigatrees provides a Force Thumbnails option that will, when enabled, hotlink the original image as its own thumbnail. No thumbnail files are created, the original images is simply shown with reduced dimensions. If you have many images on a page, this can result in slow page load speeds since each original photo must be loaded. This option does not effect profile photos as they are always hotlinked to forced thumbnails when no thumbnail is present.

Built with Gigatrees 4.5.2