Open SeaBorn49 opened 1 year ago
ShammyLevva
commented
1 year ago Interesting, how would you define a "generation"? There are lots of people who would be potentially the same generation but from radically different branches in a tree. Usually in family history software it is easier to work on moving around one family rather than jumping between branches. So I'm not entirely sure what you mean by a "generation" in this context.
SeaBorn49
commented
1 year ago There are two ways to approach it. With a primary person you could do it by relationships. First cousins, and siblings as the first level. Parents, children, aunts and uncles as the second level. Second cousins and grandparents at the third level. All others at the fourth level of coconsanguinity. The other way would be to add or subtract calendar years from the primary person's DOB.
E.g. DOB 1950. Use 1950-1970 or present date for the immediate level. 1924-1950 for the first level. 1890-1923 for the second level. 1856-1889 for the third level. And so on..
Chris Sent from the Farside..
From: Alexander Bisset @.> Sent: Saturday, August 13, 2022 12:02:10 AM To: ShammyLevva/FTAnalyzer @.> Cc: SeaBorn49 @.>; Author @.> Subject: Re: [ShammyLevva/FTAnalyzer] Error List By Generation (Issue #268)
Interesting, how would you define a "generation"? There are lots of people who would be potentially the same generation but from radically different branches in a tree. Usually in family history software it is easier to work on moving around one family rather than jumping between branches. So I'm not entirely sure what you mean by a "generation" in this context.
— Reply to this email directly, view it on GitHubhttps://github.com/ShammyLevva/FTAnalyzer/issues/268#issuecomment-1213329570, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2PFODK63DCOUWBH5VOASG3VYZ7RFANCNFSM56G6RA6A. You are receiving this because you authored the thread.Message ID: @.***>
With over 3,000 ancestors in my family tree, the error checker finds numerous errors! What would be great if you could select the generation(s) that the checker runs against! So much easier to deal with the errors and concurrently fix them at the same time!