Can we get an X-DNA Relationship Finder Tool?

+11 votes
604 views

Today, we have the great tool to find relationship between any two people, for example:

shows a 10th cousin, once removed relationship, two different ways.

This tool appears to limit its matches to three marriages (two found in this case).

It would be great to have an adjunct to this tool that limits the relationship finder to only relations where an X chromosome DNA segment could be shared.  This is, culling all paths going from a son to a father.

Is this something we could get added, perhaps as a checkbox on the form?

in WikiTree Tech by William Foster G2G6 Pilot (121k points)
Thanks for asking this question. Such a tool would be amazing.

4 Answers

+10 votes
 
Best answer
Hey William,

We are working on that currently. First will be Matrilineal relationships for mtDNA then for the X-DNA between two WikiTreer's. It's in the cue for tech...has been for a while.

Mags
by Mags Gaulden G2G6 Pilot (642k points)
selected by William Foster
Third one to do would be yDNA, which should be easy once mtDNA is completed.
Thanks for working on this. Such a x-DNA finder would be so sweet!! mtDNA relationships are easier to find than potential x-DNA relationships. It's not that simple to pick through all the different x-DNA possibilities.
+8 votes

Hi William!

If i understand correctly what you are looking for, i believe it already exists for each profile in WikiTree.

When the profile is open, you want to click on the 'Family Tree & Tools' tab.  First you will see the family tree of that person.  Scroll down below the tree to the section called Genealogy Research.  The items in that section are in alph order.  You want 'DNA Ancestors and DNA Descendants'.  

Here's something from the Help pages:

https://www.wikitree.com/wiki/Help:DNA_Ancestors

So you can find out where the person's X chromosome content could have come from (divided by % from each potential ancestor), and for each of those ancestors, you can find out which of their descendants got X material from them.  

by Shirlea Smith G2G6 Pilot (284k points)
Let me know if that answers your question somewhat, or if you need to see an example
What you point to is a list of ancestors, not a search for a DNA connection between two individuals.
You just have to take two steps to get an answer
Seems onerous to compare two lists of potentially hundreds of people and search for those that appear in both lists.  Better to just have the requested tool I proposed and which is being worked on.
+5 votes

WikiTree can tell you who could have contributed to someone’s X chromosome(s): 

https://www.wikitree.com/treewidget/Martin-11379/89#X

and WikiTree can tell you who could have inherited portions of someone’s X chromosome(s):

https://www.wikitree.com/treewidget/Denmark-218/890#X

Creating an X chromosome relationship finder was thought to be difficult (and there were other programming priorities) so we came up with a work around with the tools we had.  It was not overly difficult for WikiTree to show which descendants had taken an autosomal DNA test.  Since all autosomal DNA tests include X chromosome results, then WikiTree could show on someone’s X chromosome descendant chart which descendants had taken an X chromosome test.  Then it was just a matter of adding a [compare] link next to each X chromosome testee and linking to GEDmatch’s X chromosome One-to-one comparison utility.

To see how it works, first login to GEDmatch and then go to https://www.wikitree.com/treewidget/Denmark-218/890#X then click on [compare] next to Peter Roberts and then Helen Rice.

Sincerely, Peter

by Peter Roberts G2G6 Pilot (705k points)
edited by Peter Roberts
Keep in mind that x-DNA matches can extend many generations beyond typical autosomal DNA matches. Current generational limitations for finding autosomal relatives need to be extended for x-DNA matches.
How many generations of X chromosome ancestors would you like to see?

Consider that females inherit an exact copy of their father's x-chromosome. Inheritance from mothers can vary considerably, but we can use normal autosomal inheritance as a model. So the most extreme scenario would be inheritance from daughter-to-father-to-mother-to-father-to-mother-... etc, wherein inheritance from the father would be 100% in every other generation. Thus the genetic distance for x-DNA inheritance could be about twice as many generations as with typical autosomal generations. More precisely it could be 2 times, plus 1 the genetic distance of regular autosomal inheritance. 

Following a pattern like that in two different family trees is difficult at best, which illustrates the usefulness of an x-DNA cousin finder. This also illustrates how x-DNA inheritance can be amazing for confirming quite genetically distant ancestry.

As an example, I just found a 5GGM who contributed a quarter of my X chromosome.  2 segment matches totaling 50 cM.  No autosomal matches at all.   The (very useful, Thanks!) WikiTree X inheritance tool estimates 6.25% from that ancestor, so 4x what is expected.

My match was a 6C2R so an even longer distance down their side of the tree.

For a concrete proposal, how about extending the generations out until either 1/64 or 1/128 estimated contribution?

Hi, Richard. Just a non-WikiTree comment, which I've made before in relation to this feature, that there are as yet no accepted X chromosome inheritance baseline averages like there are for the 22 combined autosomes. The percentage estimations for the X chromosome that WikiTree displays are incorrect and can't be scientifically substantiated. I believe that the calculation is using the Coefficient of Relationship--or some slight modification--and that is not applicable to the X chromosome.

Simulations and estimates for X sharing can and have been done, but the calculations are complex and none have been accepted as a standard, to my knowledge even in forensic analysis beyond one or two generations. Probably the best paper I've seen is: Vince Buffalo, Stephen M. Mount, and Graham Coop. "A Genealogical Look at Shared Ancestry on the X Chromosome." Genetics 204, no. 1 (September 1, 2016): 57–75. https://doi.org/10.1534/genetics.116.190041. But even in those estimations (they use a Poisson-binomial approximation to the estimated recombination numbers) there are underlying assumptions about the number of times the X chromosome is likely to undergo crossover during meiosis that is somewhat in disagreement with data obtained by Blaine Bettinger using 150 actual meiosis events.

But even in the Buffalo et al. paper the extrapolation is that the odds of any two 5th cousins displaying zero X chromosome IBD sharing is over 50%, and by 6th cousins it's over 65%. Given the relatively small sampling size of the X chromosome in our consumer microarray tests (for example, the AncestryDNA v2.0 tests look at an average of 26,625 loci among the X's 156 million base pairs, so only a 0.017% coverage; Ancestry v1.0 was only 17,604 SNPs) coupled with its unique inheritance pattern, it makes genealogical assumptions based on the X chromosome extremely difficult. That's why none of our genealogy testing companies use the X for matching purposes, and only 23andMe even includes any matching xDNA centiMorgan count within the total matching reported.

Personally, I'd like to see just the opposite, that WikiTree (it is the year of accuracy, after all) go the opposite direction and, for displaying percentage X chromosome sharing, either:

  1. Apply the Buffalo/Mount/Coop algorithms to arrive at more realistic valuations (which may be impractical considering the CPU cycles that might be required).
  2. Eliminate lateral relationship displays (i.e., do away with showing a percentage on siblings, aunts/uncles, and cousins) and restrict it to ancestors only and possibly only as far as 5g-grandparents (where we hit the Buffalo et al. 35% chance of valid IBD sharing).
  3. Remove the X chromosome percentage estimates entirely since they currently have no accurate purpose and replace them with a simple icon that indicates the two individuals are related along the X chromosome inheritance path, and they may--or may not--share any actual xDNA.
Edison,

I agree with your suggestion, 100%. x-DNA inheritance is special when one finds it, but is by no means predictable.

The other 22 chromosomes are subject to recombination in a statistical manner, allowing us to make estimates of genetic distances. Not so with the x-chromosome.

X-chromosome inheritance from mothers is completely unpredictable. A child, male or female, may will inherit one x-chromosome from their mother, who has two herself. That chromosome may come from either of her x-chromosomes or some recombination of both of them. The key point is that any recombination of a mother's two x-chromosome strands is not predictable. There needs to be larger studies to know how likely these different scenarios are to occur.

Personally, I have observed both scenarios. I have found two siblings who do not share any x-DNA because they each inherited a different strand from their mother. I do think that some recombination of the mother's two x-DNA strands is probably more common, but I have no statistics to back up my personal observations.

Trying to predict x-DNA inheritance is like trying to predict next September's weather in January. We have some general idea of it, but we really don't know how it will play out.

This unpredictability is what makes finding x-DNA matches so very special, especially between distant cousins.

"Trying to predict x-DNA inheritance is like trying to predict next September's weather in January. We have some general idea of it, but we really don't know how it will play out."

Okay. I'm stealing that it's so good.  wink  And accurate. We have some almanac history to go by, but where I am along the Gulf Coast, September is the height of hurricane season...so it might be 77 degrees and beautiful, or we could have a Category 5 knockin' on the door. 

Bettinger's information indicated that the X will be passed from mother to child approximately:

  • 14% of the time intact and not recombined
  • 30.7% of the time with 1 crossover (two segments)
  • 32.7% of the time with 2 crossovers (three segments)
  • 17.3% of the time with 3 crossovers (four segments)
  • 4% of the time with 4 crossovers (five segments)
  • 1.3% of the time with 5 crossovers (six segments)

But that was admittedly a very small sample and, of course since it wasn't reported in the original data, there is no estimate of how frequently no xDNA at all is inherited.

Jim Owston wrote an informative piece in 2012 where he described his own situation where he has very little X matching with his two brothers, and he included a table with results of a request to the 23andMe Community Forum to provide their xDNA matching to known relatives. He included relationships out to 2C1R where at least five matches were documented, with the values shown in centiMorgans. Again, no matches (no xDNA sharing), no reported values, so that zero range isn't represented at all.

But the ranges shown do reflect the "weather in September" situation. For example, of 34 sibling matches, Jim's reported range was 14.7cM to 182.8cM; in 53 avuncular matches, the range was 11cM to 201cM (which is an artifact of the 23andMe calculation at the time; for other comparison services right at 196cM would be the maximum for the chromosome).

The result, though, is that X-matching can be extremely informative...but not as a tool for relationship prediction, at least not without concurrent autosomal matching. With relationships as close as full siblings, there could be zero xDNA sharing, as you noted, to 100% HIR sharing, which is a given in female siblings and of higher likelihood than zero between male siblings.

Hi Edison, Thanks for your thoughtful response.  Agreed about the uncertainty.  I took a look at that Coop et al. paper a week or two ago and what seemed notable was how few conclusions they drew.

That said, I think the WikiTree estimates are useful (and in this sense at least, accurate) as an assessment of the mean expected contribution from a given relative.  That at least is pretty simple, right?  Just based on the number of meioses in a given path.   The distribution is what is complex and makes drawing firm conclusions difficult.

To give a practical example, I have another 50 cM X match (this one is a single segment and does have multiple triangulations, unlike the 6C2R example I gave), but in this case my match does not have a very useful tree and I have not been able to find a connection.  I think the WikiTree estimates are useful for focusing my attention on the areas of my tree most likely to be candidates (and at the next level analysis using the same approach to focus my efforts to extend my matches tree).

The uncertainty was why I suggested such a low threshold (1/64 or 1/128) for inclusion.

P.S. Where this becomes even more interesting is different SNP sets for different companies and versions.  I uploaded 23andMe v3 and v5 kits to FTDNA and those only match 2 segments of 17.8 and 22.3 cM.  Hopefully my GEDmatch kit which is "all" SNPs (these kits are all based on a 30x WGS) is more useful.  This table shows how much the 23andMe v3 and v5 kits differ in X coverage, but there are similar differences for different versions at other test companies.
https://isogg.org/wiki/Autosomal_SNP_comparison_chart#X_chromosome_SNPs

Any idea if imputation is better or worse for the X chromosome compared to the autosomal chromosomes?

Mornin' Richard (at least it is here). I think your second paragraph pretty well sums up the problem: "That said, I think the WikiTree estimates are useful (and in this sense at least, accurate) as an assessment of the mean expected contribution from a given relative.  That at least is pretty simple, right?  Just based on the number of meioses in a given path."

Therein lies the rub, and the previous commentary about the Buffalo et al. paper: there is no established mean. WikiTree is using, I believe--and I've mentioned this a few times before but never had input to correct me--some flavor of the Coefficient of Relationship to calculate the percentages we see on the profiles. The CoR can't apply to the X chromosome because the CoR is based on 50% autosomal contribution from both the mother and the father. The expected contribution of the X chromosome can't be a simple divide-by-two.

Too, our testing/comparison services use half-identical regions for matching, so a female who would receive 50% of her X from her father and 50% from her father, as WikiTree correctly reports, would compare on HIRs as 100% to each. I think that sort of thing is more likely to cause confusion than would removing the percentages and just leaving the little xDNA icon to illustrate the inheritance path.

And when we try to diverge from the direct ancestral lines, it goes even farther astray from reality. We see it immediately with full brothers, whom WikiTree projects to share 100% of their X chromosomes...which almost never happens because with each ovum the mother's X has most likely gone through crossover from one to three times. Unless something like the Buffalo et al. curve-fitted simulations are used, I just don't think X chromosome sharing percentage projections are of any real use. The 50/50 assumption can't be used even as close as 1st cousin relationships.

Yep; I'm (sorta painfully) aware of the differing SNP overlaps between microarray tests. If you look at my informal Ancestry v2.0 comparison paper I linked to above, you'll see some specific data for those tests broken down in summary to the autosomes, X, Y (PAR and not), and mtDNA, with some SNP total summaries included of four revs of the Illumina default OmniExpress and GSA chips. Frankly, from the earliest days of popular microarray testing I think most people have felt that the most genealogy/population-relevant SNPs were carefully evaluated and selected for testing. That really isn't the case. And the fact that in the span of just a handful of years we're dealing with tests that have as little as 23% SNP overlap is a continuing challenge.

I've never looked specifically the X overlap among our popular microarray tests. Hm; may want to do that.

A quick aside: if you used something like WGSExtract to compile your "all SNP" GEDmatch upload, what you ended up with is a collection of SNPs for which there was at least one correspondent in the "template" commercial microarray results. In other words, you probably uploaded around 2.1 million SNPs to GEDmatch which they then "slimmed" to around 1.1 million. Those commercial "templates" should have combined for a total of about 53,000 X chromosome SNPs, which still is equivalent to only about 0.03% of the chromosome.

The dbSNP database has over 27 million SNPs cataloged on the X chromosome, and even at that we have to consider that it wasn't until last September that we saw the first telomere-to-telomere assembly of the human X (Miga et al., Nature), filling in the centromeric region and 29 previously known gaps. Those data won't hit our reference maps until the next major GRCh update, though...and the old GRCh37 reference we still use for most of genealogy had a number of corrections made in GRCh38. Genealogy is well behind the times there. The extra SNP count from my WGS helped me at GEDmatch, at least a bit, to reduce the number of probable X chromosome false matches. A number of matches fell off once there were more SNPs available to fill in the blanks.

As for relative effectiveness of imputation on the X, I really don't know. Above my pay grade.  :-)  That accuracy is predicated first and foremost by the quality and size of the cohort genomes in use at any given time and, particularly since none of our testing companies use the X only for matching (a minimum-threshold autosomal match must exist first), I have a feeling that the accuracy of imputation for the X lags behind a bit...at least when it comes to the genealogy tools we have available.

Diversity on the X chromosome is largely driven by the matrilineal line, and for that reason will vary in demography/geography from the autosomes. Some studies (like Arbiza et al., American Journal of Human Genetics, June 2014) indicate that the diversity seems to be fairly consistent within broad continental populations, but with the X diversity notably lower in both European and East Asian populations. So the autosomal imputation references carried over to the X at that level should be fairly accurate, and most accurate for European/East Asian cohorts. The flip side is that the lack of diversity also implies those populations will have a more difficult time making genealogically-relevant determinations about X inheritance as the generations go back in time.

Good morning (here too, I'm in CA) Edison.  Thanks for another informative comment.  BTW, is there any established convention HERE for including quotes so I can respond to specific points with context?

I don't think WikiTree is using the CoR for X calculations.   If you look at the numbers they give it seems clear that they are just dividing the expected contribution by two when there are two parents contributing (for female children).  Which seems like a good approach.  The CoR does not account for sex so they are only loosely related (the CoR divides by two for all children).

Again, I really do think the number they give is an appropriate EXPECTED mean contribution.  One good sanity check is to remember that for each generation of ancestors the sum of the expected mean contributions of all ancestors should be 100%. (I may be eliding some subtleties here, but I think the basic idea holds well enough to make it worth using).

Agreed that the differences between males and females is an issue here for the half-identical matching and can be confusing.

I don't see where WikiTree is projecting brothers to share 100% of the X chromosome (can you point me to that?).  What I see is WT saying each brother gets 100% of his X from his mother.  But it says nothing about WHICH 100%.

Have I not been clear about the utility of using the expected contributions for prioritizing which regions of the tree to focus on for X matches?  I think that is an important use which would make removing those numbers a mistake.  For males it is obvious not to look at the paternal side at all, but things quickly become less obvious as you go deeper into the tree.

It's worth taking a look at the X SNP matching statistics for different kits (see the ISOGG link I gave).  There are dramatic differences.  What I find unbelievable is that the different versions from the same supplier vary so much.  Are they taking sufficient measures to enable the different versions of their kits to match well? (having just skimmed your Ancestry document--Thanks!--I see you are all over this topic in general)

Your WGSExtract discussion is spot on.  That was why I put scare quotes around "all."

Mornin' again.  :-) Peter Roberts uses his own profile quite a bit in WT DNA examples, so I don't think he'll mind me doing so. If you look at Roberts-7085  you'll see that Peter has two of his brothers shown in the "DNA Connections" panel. Consistent throughout WikiTree, the brothers display as sharing 50% of their atDNA and 100% of their xDNA. He also has one sister listed, shown as "Anonymous," and she is displayed as 50% atDNA, 50% xDNA, also consistent with female siblings across WT. These are sharing amounts with Peter and his siblings, not their parents, as is evidenced by the sharing amounts listed for other relationships on down the page, and that Peter's mother and father each have their own, separate listings in the panel on his profile.

And starting at Peter's profile, you can find other X-sharing family members from whom he is not directly descended. For example, a maternal uncle (25% atDNA and 50% xDNA with Peter); Peter's great-aunt (his maternal grandmother's mother's daughter, 12.5% atDNA and 25% xDNA); Peter's 4g-grandaunt (Denmark-441, 0.78% atDNA and 6.25% xDNA), and more.

I really don't have a ton of heartburn over the direct ancestor xDNA percentages. I can take it or leave it. That said, a lot of WikiTreers view the "DNA Connections" panel as actual "DNA Matches." We see it regularly in G2G questions, and years after its implementation it still causes confusion.

As to prioritizing which areas of the tree are relevant to xDNA, personally I feel a simple, colored fan chart does a pretty good job; like this female inheritance chart and male inheritance chart, for example. The added clutter of displaying unfounded percentage numbers for my 4th great-grandaunt just doesn't seem helpful to me. With xDNA, it's the inheritance path that's vital, that Fibonacci sequence pattern.

Then again, I'm with the testing companies on this and will never assume an xDNA match can be attributed to any specific genealogical ancestor without autosomal corroboration. All the testing companies deal with xDNA as a modifier to atDNA, not a standalone matching opportunity. As mentioned before, the X--particularly in populations of European descent--is less diverse than autosomal DNA and more prone to have population-level artifacts that have no associative bearing in the genealogical timeframe.

Maybe that's the crux of my difficulty. WikiTree teaches members that the X chromosome has some special properties when it comes to any two males who match: https://www.wikitree.com/wiki/Help:Advanced_DNA_Confirmations. As written it is unsubstantiated and incorrect, and I suppose I fear we're only further expanding myths about the usefulness and application of certain types of DNA to genealogy.

Good morning again.  Thanks for clarifying!

I definitely agree with your points as apply to the DNA connections panel (I had not been looking at that).  Those shared X estimates aren't mean expected values.  They are simply wrong.  It seems like a more correct calculation is possible.  Just treat female children as autosomal (not strictly true because of lack of recombination between father and daughter) and male children as a special case where the parents are treated differently.  My sense is brothers should have an expected match of 50% with the distribution being roughly normal from 0 to 100, but I have no idea what the standard deviation would be and that is important.  And then there is the problem of how to extend this over multiple generations.  What do you think?

Those fan charts are indeed useful (I had run across them before, but kept looking because I did not want to do by hand and wanted percentages at different levels).  Do you know of any tools which generate the X versions for my own pedigree automatically?  I was looking at the WikiTree tool as a good automatic approach, but the fan chart is even easier to visualize.  Perhaps vary the intensity of the color by the expected percentage?

The lack of the percentages really is a weakness though.  At the 5GGP leaves on the male chart you gave the percentages vary by a factor of 8 from 1/64 to 1/8.  That is worth caring about!  Those MFM groupings really matter for tree depth of X matches.  

I don't consider it a coincidence that my known 50 cM X match occurred through a 1/16 5GGM.  Note that match does not have an autosomal match with me (which is a decent possibility at the 5GGP level).

That is why I strongly disagree with your (and the testing companies) policy of only looking at X matches which also have an autosomal match.  If not for GEDmatch's ability to look at this I would have missed out on a match which accounts for a quarter (!) of my X chromosome.  I was just lucky she had a tree which was almost as comprehensive as mine in that spot.  I had just fleshed out a collateral line due to chasing down an Ancestry Thruline which was the only thing that allowed me to find the link (a single person who was a FMF grandniece of my 5GGM).

I agree with your X diversity point as a possible issue for small X matches, but the ability of X matches to persist does make them potentially valuable at ranges beyond those we typically see for the autosome.  I hope we can agree that a 50 cM (two segments of 36.4 and 14.1 cM with a 53 Mbp gap between them) is unlikely to be a population-level artifact (especially given that clustering shows my tree not to be very endogamous for the autosome).

Now I just need to track down my other 50 cM X match (a single 52.2 cM segment in a different spot).  He does have an autosomal match (28 cM), but appears likely to be on the other side of a current brick wall.  I think Ireland is where family trees go to die.  My maternal grandmother comes from there which is why I am so concerned with X matches.  They seem like a good possibility to help break through there (I also have some autosomal matches which appear to be there but I can't quite connect them yet).  In particular, for my unknown 50 cM match I think the ability to focus on specific lines might help narrow the search.

I do think the X chromosome matches are special for males, but just not in the way WikiTree seems to be promoting.  The specialness comes from the ability to have a generation without meiosis for sons and the overall effect of MFM links in the tree given the lack of recombination for the father's X passed to a daughter.

Thank you for a very interesting conversation!

P.S. Looking more closely at that final WikiTree link, I think they are right about no triangulation being necessary for the male-male X match.  It really does not say more than that as far as I can tell.  I think people are reading more into that than it truly says.  One definitely needs to be cautious about considering small matches as conclusive proof.  Especially if endogamy is present.

I actually think the mtDNA statement is worse since though strictly true they ignore the highly relevant fact that mtDNA is smaller and varies much less than autosomal (or X and Y for that matter) DNA so the MRCAs you find might very well be in the mists of history (thousands of years).  Perhaps useful for narrowing searches, or refuting possible maternal ancestors though.

To add some numbers to my complaint about DNA vendor policies concerning only giving X chromosome matches when there is an autosomal match as well, here are some statistics from my GEDmatch X matches.

8 X matches which also have an autosomal match (and 1 is a duplicate kit).  Of those only 1 has both over 10 cM.  2 have a>10 and X<10.  4 (1 dup) have X>10 and a<10.  1 has both<10.

That is out of 384 total  X matches.  130 of those being 10 cM or  larger with 13 over 30 cM (only 1 with an autosomal match as well) and 49 over 20 cM.

I think losing that amount of information (presenting 8 out of 384 matches would be the result here!) is unacceptable.  In particular, excluding those 12 30+ cM X matches would be a major loss.  Those include the 6C2R I was able to connect using her tree which allowed me to assign that 36 cM match (along with her other 14 cM X match) to a specific 5GGM.

I can only imagine how many possible X matches I am missing out on elsewhere because of that policy.

Compare those numbers to my two FTDNA kits.

My 23andMe v3 kit shows 54 X matches on FTDNA, but when downloaded using DNAGedcom I only see 10 (I need to check my thresholds, but I think the issue is FTDNA returns very small matches), 2 of which are over 10 cM (one is 52.2 cM though) and all 10 over 6 cM (probably the threshold I used).

My 23andMe v5 kit shows 81 matches on FTDNA and 88 from DNAGedcom (I used minimum as the threshold here and there are some multiple matches).  Of those none are above 8 cM and only 6 are above 5 cM.  It appears the 23andMe v5 chip is terrible for X matching on FTDNA.  Which is interesting given that the v5 kit returned 4563 autosomal matches vs. 3293 for the v3 kit.  Here is the ISOGG SNP comparison again.
https://isogg.org/wiki/Autosomal_SNP_comparison_chart#X_chromosome_SNPs

I think that also answers the question whether there is effective X imputation done at FTDNA.

Given the relative sizes of the databases involved that is a large number of potential missing matches.

Edison, do you still think only returning X matches when an autosomal match is present is a good policy?

+3 votes

I made an x finder and by chance i even named it x finder x finder (pathfindergenealogytools.blogspot.com)

by Marilynn Atkinson G2G Rookie (290 points)

mom finder (pathfindergenealogytools.blogspot.com)

pop finder (pathfindergenealogytools.blogspot.com)

I also made a mom and pop finder for shared haplogroups gives exact relationship paths. i am excited that anyone was hoping for tools to do that

Greg Clark’s X Friends lets you put in your WikiTree ID and lets you know which of your relatives (in WikiTree) could be an X-DNA match with you.  It also works with a GEDCOM.  https://www.wikitree.com/g2g/1523948/introducing-the-x-friends-app

Related questions

+6 votes
1 answer
+8 votes
0 answers
+3 votes
0 answers
201 views asked Apr 25, 2019 in WikiTree Tech by Living Anderson G2G6 Mach 7 (79.4k points)
+9 votes
3 answers
+8 votes
3 answers
+3 votes
0 answers
157 views asked Jun 18, 2017 in WikiTree Tech by Lewis Buttery G2G2 (2.3k points)

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright

...