You can configure your family tree to make use of the photos you have linked to in your GEDCOM file. Depending on how you want to use your family tree, there are several options to consider.
Force Thumbnails Link Photos (Local Paths) Link Photos (Relative Paths) Treat Relative Paths As Local
If you plan on moving your family tree to a hosting service so it is available online, you will need to make sure that the
OBJE.FILE fields in your GEDCOM file for any photos you want to link to, use either an external path (i.e.
http://domain.com/folder/photo.jpg) or a relative path (i.e.
folder/photo.jpg or simply
photo.jpg). External paths are always linked to so there are no options to consider. It is not possible to link to local paths (i.e.
c:/folder/photo.jpg) from an online server, so you should disable linking to these here. You should also disable linking to relative paths as though they were local links for the same reason. This will force relative links to be linked to externally. If you do not plan on uploading your photos to your hosting server, then you can disable linking to relative photos entirely here as well. If you do plan on linking to your relative photos externally, you can set the Photo Images URL in the External URLs section below to include your hosting server's domain explcitly (i.e.
http://domain.com/) or you may leave it blank to use the same relative path on your hosting server. Ideally, relative paths found in your GEDCOM file should NOT be preceded with a slash (i.e.
\). See the description under the External URLs for more information on how to setup these paths.
If you want to be able to link to your photos online, but your GEDCOM file uses local paths, making that impossible, a new
OBJE._PATH field is supported that allows you to set up a relative path while leaving your
OBJE.FILE field pointing to your local path. This way your genealogy application will continue to work correctly with your local photos and Adam will be able to use the relative paths for online linking. The
OBJE._PATH will always take precedence over the
If, on the other hand, you plan to view your family tree offline, directly from your hard drive, then your
OBJE.FILE fields can be external, local or relative. Again, external links are always linked to so there are no options to consider. You will also want to enable linking to both local paths and relative paths, and treating relative paths as local paths. In this way, all links will be set correctly.
Links to photos that include valid extensions (i.e.
gif) will use the source image as its thumbnail when the Force Thumbnails option is enabled. Otherwise a default image will be used. Forcing thumbnails requires loading the entire image, scaling it down proportionally so that it is not distorted and then cropping the bottom, if necessary, to fit within a fixed-sized, square bounding box. When a lot of photos are being loaded like this, especially if they are large, it may take a long time for your page to load. You can disable thumbnail forcing to eliminate this problem, but then you don't have recognizable thumbnails. To get around this problem Adam supports an additional GEDCOM extension. The
OBJE._PIC field can be used to set the paths for your thumbnail images. The paths can be external, relative or local depending on how you want to use them, and a seperate Photo Thumbnails URL can be set in the External URLs section below for use with relative paths.