Using this site

Untitled Document

Trees and Branches


Trees are listed under Info > Trees as illustrated below. There are currently three trees:

  1. Roy~Royes,
  2. Roy Miscellaneous
  3. Royes Miscellaneous

though the last two are "collections" of data rather than a single "tree".

The main tree is Roy~Royes, designated "rr_tree" and refers to the complete collection of data about inter-related people, families, notes, linked media, etc. based on the ancestors, descendants, cousins of Maurie Roy and May Royes.

Roy and Royes (and related) people who may be connected to the Roy~Royes tree are maintained in two other "trees" - links in the More drop-down menu will list names included in that data. Some people in these two "trees" are there simply because they are Australian residents with the same surnames as ours (out of "curiosity"), others because it might be possible to link their family into one of ours.

You will see on many pages a choice of trees (including "All"). Keep an eye on this when you are doing searches or browsing. Have a look at Info > Statistics and play with the Tree options to get "a feel" for these differences.



Branches are subsets within the Roy~Royes tree and you can examine what branches there are and who is in which branch by using the Info > Branches link.

Branches are constructed in different ways - spouses are included:

  • based on a key person and their pedigree (ancestor) and descendant lines (Eg, Hougham - based on Solomon Hougham b.1475);
  • based on a "tree top" (earliest known ancestor) and their descendant line (Eg, Royes based on John Royes; Roy based on James Roy); or
  • based on a registered user in such a way that they and their partner's ancestors are shown, together with their descendants - this is usually constructed by choosing one of their children as the key person.

A person can belong to more than one branch.

People who are granted access to information about living people have this privilege for their branch only - even if they belong to more than one branch. (This is more a technical matter than one of policy.)