#1202 Found Ancestor Statistics


What I would really love is a statistics report that shows per generation how much of the possible ancestors are found.

Generation#, Found Ancestors#, Found Percentage %, Possible Ancestor#, Missing Ancestors#,
1,1,100%, 1,0
3,3,75%, 4,1
Calculated,Gedcom data, calculated, calculated, calculated

The above report gives you perfect insight in how much of your ancestors have been found


  • Stephen Arnold

    Stephen Arnold - 2010-05-01

    I don't wish to appear to be stupid, but after spending more than 5 minutes reviewing what you are asking for, I'm still stumped. How would you ever know how many ancestors you have at each level? How would ever you know how many are missing? Despite extensive research, I'm never sure how many relatives I've had. Heck, I'm not even sure how many children I've fostered - are you?

    Perhaps you can explain from whence this data would emanate?

  • Aldo

    Aldo - 2010-05-01

    Well most of the columns are calculated. Only how many ancosters are found should come from the gedcom file. E.g. starting with myself being generation 1 would lead to row1: generation 1, 1 found as I know my name ;-), that's 100% found, generation 1 consist of 1 person. None is missing

    Row 2 would look like: generation2, 2 found as I know my parents names, that's 100% found, generation 2 consists of 2 persons, none is missing

    Row 3 would look like generation 3, 3 found as I don't know one of my grandparants (just an example), 75% as the everybody has 4 grandparents and 3 out of 4 is 75%, possible ancestors is as mentioned 4, missing ancestors is ofcouse 1.

    So the calculation would be:
    Column 1: would be a simple 1,2,3,4 etc.(limited ofcourse as you don't have a tree till adam and eve ;-)
    Column 2: would come from the entries in the gedcom. A query can be used that generates a ancestor list and then some calculation has to be done on the entries per generation.
    Column 3: is column 2 devided by column 4
    Column 4: is a simple expotential calculation. generation 1 is 1, gen. 2 is 2, gen. 3 is 4, gen. 4 is 8, gen 20 is 524.288!
    Column 5: is column 4 minus column 2

    You can put it into a graph as well. see http://azeeland.blogspot.com/2005/07/here-you-see-my-score-in-finding-my.html

    The item that makes the above go wrong is when brother and sisters or nephew and cousins form a pair. I hope that hasn't happend that often :-)

  • Stephen Arnold

    Stephen Arnold - 2010-05-01

    Gotcha. Although this already exists graphically within the Circle Diagram. In fact, we note to our users that we believe this to be one, if not the best diagrams/reports available as it very graphically displays areas of research needed.

    Have you used it? We do so nearly daily, for instance, my father:

    I'm not sure of what additional value your ancestral written report would be beyond this as the circle diagram (fan chart as originally titled and still named so in the code) is very dynamic, can be navigated easily and fluidly and it can be printed for static review.

  • Aldo

    Aldo - 2010-05-02
    • priority: 5 --> 1
  • Aldo

    Aldo - 2010-05-02

    The Circle Diagram is definitly THE most powerfull report enabeling me to get an overview on my ancestors. I love it!

    The value of my suggested report is in it, that it provides some metrics on the ancestor tree. Maybe it is just me that likes to know how much my research has resulted into. I now export my gedcom to a genealogy program which does provide this kind of information. I then process it in excel.

    It looks like:http://4.bp.blogspot.com/_dguy8R15B7k/S90wr16dWcI/AAAAAAAAADQ/Vs0nO4pGdnU/s1600/AncestorChart.jpg

    If there is a way to retreive this information from phpgedview it would make my life somewhat easier ;-) But I guess more users should feel the usefullness of such a statistics report. So if someone reads this who supports this thought. Please let it be known.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks