I had the same problem, neither the zipped or txt file from ancestryDNA worked. Any solutions? Jan Janeth A Campbell Retired Researcher and Educator PO Box 13877 Tallahassee, Florida 32317-3877 *J*[email protected] <[email protected]> On Sun, Oct 8, 2017 at 4:41 PM, <[email protected]> wrote: > Send GENEALOGY-DNA mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists3.rootsweb.ancestry.com/mailman/listinfo/genealogy-dna > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of GENEALOGY-DNA digest..." > > > Today's Topics: > > 1. Working with high largest X-matches on GEDmatch (Wesley Johnston) > 2. Ancestry upload to Family Tree DNA - problem (Genealice) > 3. Re: Ancestry upload to Family Tree DNA - problem (Nancy Custer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 8 Oct 2017 12:54:56 +0000 (UTC) > From: Wesley Johnston <[email protected]> > To: DNA Genealogy Mailing List <[email protected]> > Subject: [DNA] Working with high largest X-matches on GEDmatch > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > I am looking to see just what a high X-match that has no shared atDNA can > tell us about shared ancestral lines. Clearly this is pushing back very far > in time. I am using a female kit that is of pure Czech ancestry as far back > as we know (roughly in the late 1600's and early 1700's). On her 6-gen > X-inheritance chart, we know at least the name of 9 of the 13 X-ancestors > and know the spouse's surname in all 13. So the challenge of finding a > matching line is narrowed to Czech or Slavic lines. > > But that is not the problem that I am running into on GEDmatch. The > problem is that different GEDmatch tools are presenting conflicting > results. The kits come from different test companies, so that I am not sure > if this is a factor. > > To allow anyone wanting to repeat this to do so, I am going to include kit > numbers. The kit of the focus person is T685302. > > Here are the steps that I have done. > 1 - Identify X-DNA matches, sorted by largest X-DNA cM. > I used the free one-to-many and then sort descending on largest X-DNA cM. > Setting aside immediate family members, the top 10 matches range from 16 to > 21 largest X-DNA cMs, and all but the top one show zero total atDNA cMs > (the top one M052745 has 5.1). > 2 - Do a one-to-one X-DNA comparison of some of the top 10. > Clicking on the X in the X-DNA Details column, you would expect to see the > same information shown in the one-to-one comparison as in the sorted > one-to-many. And in some cases, the X 1:1 does show about the same (an 18.8 > largest X-DNA A916434 on the 1:many shows as 18.7 on the X 1:1). But in > some cases, the X-DNA 1:1 shows zero shared X-DNA (an 18.3 largest X-DNA > M131017 on the 1:many shows as no match at all on the X 1:1). > So I tried dropping the SNP threshold with M131017 on the X 1:1 to 100 > SNPs and the minimum cMs to 1 (which should not be necessary if there is > indeed a largest X shared 18.3 cM as the 1:many list shows). And this does > generate a list of shared ranges on the X, the largest of which is 5.4 cM > (162 SNPs) by cMs or by SNPs 3.5 cM (295 SNPs). So clearly this is a > radical difference from what the 1:many list is showing when it reports a > largest shared X of 18.3 cM). > 3 - Create a Tag Group for the highest matches. > I used the Tier1 1 1:many tool to create the group, setting the option to > filter by X (instead of autosomal) with offset 0, limit 500 (the minimum > allowed) and cM size 3 (the minimum allowed. This gives a completely > different (from step 1) top 10 list. Where the free 1:many had largest cMs > of 16 or more for the top 10, the Tier1 1:many showed no one (other than > close family) with a largest cM of more than 11.2. > > So I then tried the Tier1 1:1 on autosomal and setting to the minima and > sorting on the largest X (trying to re-create the list in step 1. But since > the Tier1 1:1 does not include atDNA matches of zero, neither one of these > methods was able to find the same high largest X but low atDNA matches that > the free 1:1 tool found. > Nevertheless, I created a tag group of those X-matches (from the atDNA > version of the Tier1 1:1) who had the highest total X cMS (20.0 and above, > minus immediate family). This tag group has 20 members. > 4 - Run the X-DNA Matrix Comparison for this tag group. > This was a real shock. Since the tag group had been specifically created > from a 1:many list of the X-DNA matches of T685302 who had 20.0 or more > total cMs, you would expect to see a number in every cell of T685302's > row/column. But 8 of the 19 cells are empty. Going back to the Tier1 1:1 > list used to create this tag group, one of these empty cells is the second > highest total cMs (40.8), but the largest for this match is just 6.4 and > thus under the threshold of 7 cM for the matrix, which explains the empty > cell. > > > The bottom line seems to me to be implicit and explicit threshold > differences among the tools. I really would like to work with the top 10 > from the free 1:many, but even the free X 1:1 conflicts with some of the > ones shown in that list. And the Tier1 1:many does not even discover these > matches (apparently because the Tier1, even when choosing the X option) > still has some implicit atDNA threshold). > Choosing these low-autosomal / high largest X matches as a target is a > challenge in the first place. But the GEDmatch tools make it extremely more > challenging when they do not allow exploration of those matches. > Clearly having more ability to twist the knobs on GEDmatch would help. But > the fact that (step 1 and step 2) there are very significant conflicts > between one GEDmatch tool showing? 18.3 cM of a largest shared X and > another showing nothing more than 5.4 cM for the same two people seems to > be more than just finding the right settings of the knobs. > > > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 8 Oct 2017 21:02:08 +0100 > From: Genealice <[email protected]> > To: <[email protected]> > Subject: [DNA] Ancestry upload to Family Tree DNA - problem > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > > > OK, I fully admit I joined this list because a problem has cropped up and > I'm posting straightaway. But I hope it will be of interest to the mailing > list and thank you for having me! > > > > I am trying to do an autosomal transfer, uploading an Ancestry.com raw data > file to Family Tree DNA. However I keep on getting the following message > > > > "The specified file 'Ancestry dna.txt' could not be uploaded. The file is > an > unsupported version or in a corrupt/malformed format. Please place an order > for Family Finder <https://www.familytreedna.com/products/family-finder> > or > download the file and try again." > > > > Looking on the FTDNA message boards this seems to be a common problem. > There > seem to a number of different theories over this: that is on FTDNA's side. > That it is Ancestry.com and the files are smaller than they should be. That > it is to do with the header. I have tried replacing the header with that > suggested on the message board but it made no difference. > > > > I have posted it on Gedmatch with no problem at all but I understand it > allows for more variations in the raw data. > > > > The header on the Ancestry data I have is as follows: > > > > #AncestryDNA raw data download > > #This file was generated by AncestryDNA at: 10/07/2017 01:20:13 UTC > > #Data was collected using AncestryDNA array version: V2.0 > > #Data is formatted using AncestryDNA converter version: V1.0 > > #Below is a text version of your DNA file from Ancestry.com DNA, LLC. THIS > > #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL > RESEARCH > > #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. > THE > EXPORTED DATA IS > > #SUBJECT TO THE AncestryDNA TERMS AND CONDITIONS, BUT PLEASE BE AWARE THAT > THE > > #DOWNLOADED DATA WILL NO LONGER BE PROTECTED BY OUR SECURITY MEASURES. > > #WHEN YOU DOWNLOAD YOUR RAW DNA DATA, YOU ASSUME ALL RISK OF STORING, > > #SECURING AND PROTECTING YOUR DATA. FOR MORE INFORMATION, SEE ANCESTRYDNA > FAQS. > > # > > #Genetic data is provided below as five TAB delimited columns. Each line > > #corresponds to a SNP. Column one provides the SNP identifier (rsID where > > #possible). Columns two and three contain the chromosome and basepair > position > > #of the SNP using human reference build 37.1 coordinates. Columns four and > five > > #contain the two alleles observed at this SNP (genotype). The genotype is > reported > > #on the forward (+) strand with respect to the human reference. > > rsid chromosome position allele1 allele2 > > > > I am not a tekkie and just want to get on Family Tree DNA. Can anyone help > me with this? > > > > Thank you so much! > > > > Alice > > > > > > > > ------------------------------ > > Message: 3 > Date: Sun, 8 Oct 2017 15:41:39 -0500 > From: Nancy Custer <[email protected]> > To: <[email protected]> > Subject: Re: [DNA] Ancestry upload to Family Tree DNA - problem > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > You will need the zipped file for upload not the txt file. Some browsers > will unzip your file and put the txt file in your download folder and the > original zip file in the trash. > > Look in your trash file for the zipped file and choose that for upload to > FTDNA. Of course, move the zipped file out of the trash first?? > > If you don't find the zip file in your trash folder, you can set your > browser not to open/unzip files on download. Then download again. In > Safari, that option is under Preferences in the first screen. I leave mine > set that way all the time. > > Sent from my iPhone > > > On Oct 8, 2017, at 3:02 PM, Genealice <[email protected]> > wrote: > > > > Hi, > > > > > > > > OK, I fully admit I joined this list because a problem has cropped up and > > I'm posting straightaway. But I hope it will be of interest to the > mailing > > list and thank you for having me! > > > > > > > > I am trying to do an autosomal transfer, uploading an Ancestry.com raw > data > > file to Family Tree DNA. However I keep on getting the following message > > > > > > > > "The specified file 'Ancestry dna.txt' could not be uploaded. The file > is an > > unsupported version or in a corrupt/malformed format. Please place an > order > > for Family Finder <https://www.familytreedna.com/products/family-finder> > or > > download the file and try again." > > > > > > > > Looking on the FTDNA message boards this seems to be a common problem. > There > > seem to a number of different theories over this: that is on FTDNA's > side. > > That it is Ancestry.com and the files are smaller than they should be. > That > > it is to do with the header. I have tried replacing the header with that > > suggested on the message board but it made no difference. > > > > > > > > I have posted it on Gedmatch with no problem at all but I understand it > > allows for more variations in the raw data. > > > > > > > > The header on the Ancestry data I have is as follows: > > > > > > > > #AncestryDNA raw data download > > > > #This file was generated by AncestryDNA at: 10/07/2017 01:20:13 UTC > > > > #Data was collected using AncestryDNA array version: V2.0 > > > > #Data is formatted using AncestryDNA converter version: V1.0 > > > > #Below is a text version of your DNA file from Ancestry.com DNA, LLC. > THIS > > > > #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL > > RESEARCH > > > > #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. > THE > > EXPORTED DATA IS > > > > #SUBJECT TO THE AncestryDNA TERMS AND CONDITIONS, BUT PLEASE BE AWARE > THAT > > THE > > > > #DOWNLOADED DATA WILL NO LONGER BE PROTECTED BY OUR SECURITY MEASURES. > > > > #WHEN YOU DOWNLOAD YOUR RAW DNA DATA, YOU ASSUME ALL RISK OF STORING, > > > > #SECURING AND PROTECTING YOUR DATA. FOR MORE INFORMATION, SEE > ANCESTRYDNA > > FAQS. > > > > # > > > > #Genetic data is provided below as five TAB delimited columns. Each line > > > > #corresponds to a SNP. Column one provides the SNP identifier (rsID > where > > > > #possible). Columns two and three contain the chromosome and basepair > > position > > > > #of the SNP using human reference build 37.1 coordinates. Columns four > and > > five > > > > #contain the two alleles observed at this SNP (genotype). The genotype > is > > reported > > > > #on the forward (+) strand with respect to the human reference. > > > > rsid chromosome position allele1 allele2 > > > > > > > > I am not a tekkie and just want to get on Family Tree DNA. Can anyone > help > > me with this? > > > > > > > > Thank you so much! > > > > > > > > Alice > > > > > > > > > > > > > > ------------------------------- > > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without > the quotes in the subject and the body of the message > > > > > ------------------------------ > > Subject: Digest Footer > > To contact the GENEALOGY-DNA list administrator, send an email to > [email protected] > > To post a message to the GENEALOGY-DNA mailing list, send an email to > [email protected] > > __________________________________________________________ > To unsubscribe from the list, please send an email to > [email protected] > with the word "unsubscribe" without the quotes in the subject and the body > of the > email with no additional text. > > > ------------------------------ > > End of GENEALOGY-DNA Digest, Vol 12, Issue 668 > ********************************************** >
The FTDNA error message is saying that they received a .txt file. Try downloading again from Ancestry. Do not open the file; just send it directly to FTDNA as you received it. Good luck! Doris On Sun, Oct 8, 2017 at 4:53 PM, Jan Campbell <[email protected]> wrote: > I had the same problem, neither the zipped or txt file from ancestryDNA > worked. > > Any solutions? > > Jan > > Janeth A Campbell > > Retired Researcher and Educator > PO Box 13877 > Tallahassee, Florida 32317-3877 > > *J*[email protected] <[email protected]> > > > On Sun, Oct 8, 2017 at 4:41 PM, <[email protected]> > wrote: > > > Send GENEALOGY-DNA mailing list submissions to > > [email protected] > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists3.rootsweb.ancestry.com/mailman/listinfo/ > genealogy-dna > > or, via email, send a message with subject or body 'help' to > > [email protected] > > > > You can reach the person managing the list at > > [email protected] > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of GENEALOGY-DNA digest..." > > > > > > Today's Topics: > > > > 1. Working with high largest X-matches on GEDmatch (Wesley Johnston) > > 2. Ancestry upload to Family Tree DNA - problem (Genealice) > > 3. Re: Ancestry upload to Family Tree DNA - problem (Nancy Custer) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sun, 8 Oct 2017 12:54:56 +0000 (UTC) > > From: Wesley Johnston <[email protected]> > > To: DNA Genealogy Mailing List <[email protected]> > > Subject: [DNA] Working with high largest X-matches on GEDmatch > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset=UTF-8 > > > > I am looking to see just what a high X-match that has no shared atDNA can > > tell us about shared ancestral lines. Clearly this is pushing back very > far > > in time. I am using a female kit that is of pure Czech ancestry as far > back > > as we know (roughly in the late 1600's and early 1700's). On her 6-gen > > X-inheritance chart, we know at least the name of 9 of the 13 X-ancestors > > and know the spouse's surname in all 13. So the challenge of finding a > > matching line is narrowed to Czech or Slavic lines. > > > > But that is not the problem that I am running into on GEDmatch. The > > problem is that different GEDmatch tools are presenting conflicting > > results. The kits come from different test companies, so that I am not > sure > > if this is a factor. > > > > To allow anyone wanting to repeat this to do so, I am going to include > kit > > numbers. The kit of the focus person is T685302. > > > > Here are the steps that I have done. > > 1 - Identify X-DNA matches, sorted by largest X-DNA cM. > > I used the free one-to-many and then sort descending on largest X-DNA cM. > > Setting aside immediate family members, the top 10 matches range from 16 > to > > 21 largest X-DNA cMs, and all but the top one show zero total atDNA cMs > > (the top one M052745 has 5.1). > > 2 - Do a one-to-one X-DNA comparison of some of the top 10. > > Clicking on the X in the X-DNA Details column, you would expect to see > the > > same information shown in the one-to-one comparison as in the sorted > > one-to-many. And in some cases, the X 1:1 does show about the same (an > 18.8 > > largest X-DNA A916434 on the 1:many shows as 18.7 on the X 1:1). But in > > some cases, the X-DNA 1:1 shows zero shared X-DNA (an 18.3 largest X-DNA > > M131017 on the 1:many shows as no match at all on the X 1:1). > > So I tried dropping the SNP threshold with M131017 on the X 1:1 to 100 > > SNPs and the minimum cMs to 1 (which should not be necessary if there is > > indeed a largest X shared 18.3 cM as the 1:many list shows). And this > does > > generate a list of shared ranges on the X, the largest of which is 5.4 cM > > (162 SNPs) by cMs or by SNPs 3.5 cM (295 SNPs). So clearly this is a > > radical difference from what the 1:many list is showing when it reports a > > largest shared X of 18.3 cM). > > 3 - Create a Tag Group for the highest matches. > > I used the Tier1 1 1:many tool to create the group, setting the option to > > filter by X (instead of autosomal) with offset 0, limit 500 (the minimum > > allowed) and cM size 3 (the minimum allowed. This gives a completely > > different (from step 1) top 10 list. Where the free 1:many had largest > cMs > > of 16 or more for the top 10, the Tier1 1:many showed no one (other than > > close family) with a largest cM of more than 11.2. > > > > So I then tried the Tier1 1:1 on autosomal and setting to the minima and > > sorting on the largest X (trying to re-create the list in step 1. But > since > > the Tier1 1:1 does not include atDNA matches of zero, neither one of > these > > methods was able to find the same high largest X but low atDNA matches > that > > the free 1:1 tool found. > > Nevertheless, I created a tag group of those X-matches (from the atDNA > > version of the Tier1 1:1) who had the highest total X cMS (20.0 and > above, > > minus immediate family). This tag group has 20 members. > > 4 - Run the X-DNA Matrix Comparison for this tag group. > > This was a real shock. Since the tag group had been specifically created > > from a 1:many list of the X-DNA matches of T685302 who had 20.0 or more > > total cMs, you would expect to see a number in every cell of T685302's > > row/column. But 8 of the 19 cells are empty. Going back to the Tier1 1:1 > > list used to create this tag group, one of these empty cells is the > second > > highest total cMs (40.8), but the largest for this match is just 6.4 and > > thus under the threshold of 7 cM for the matrix, which explains the empty > > cell. > > > > > > The bottom line seems to me to be implicit and explicit threshold > > differences among the tools. I really would like to work with the top 10 > > from the free 1:many, but even the free X 1:1 conflicts with some of the > > ones shown in that list. And the Tier1 1:many does not even discover > these > > matches (apparently because the Tier1, even when choosing the X option) > > still has some implicit atDNA threshold). > > Choosing these low-autosomal / high largest X matches as a target is a > > challenge in the first place. But the GEDmatch tools make it extremely > more > > challenging when they do not allow exploration of those matches. > > Clearly having more ability to twist the knobs on GEDmatch would help. > But > > the fact that (step 1 and step 2) there are very significant conflicts > > between one GEDmatch tool showing? 18.3 cM of a largest shared X and > > another showing nothing more than 5.4 cM for the same two people seems to > > be more than just finding the right settings of the knobs. > > > > > > > > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Sun, 8 Oct 2017 21:02:08 +0100 > > From: Genealice <[email protected]> > > To: <[email protected]> > > Subject: [DNA] Ancestry upload to Family Tree DNA - problem > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset="us-ascii" > > > > Hi, > > > > > > > > OK, I fully admit I joined this list because a problem has cropped up and > > I'm posting straightaway. But I hope it will be of interest to the > mailing > > list and thank you for having me! > > > > > > > > I am trying to do an autosomal transfer, uploading an Ancestry.com raw > data > > file to Family Tree DNA. However I keep on getting the following message > > > > > > > > "The specified file 'Ancestry dna.txt' could not be uploaded. The file is > > an > > unsupported version or in a corrupt/malformed format. Please place an > order > > for Family Finder <https://www.familytreedna.com/products/family-finder> > > or > > download the file and try again." > > > > > > > > Looking on the FTDNA message boards this seems to be a common problem. > > There > > seem to a number of different theories over this: that is on FTDNA's > side. > > That it is Ancestry.com and the files are smaller than they should be. > That > > it is to do with the header. I have tried replacing the header with that > > suggested on the message board but it made no difference. > > > > > > > > I have posted it on Gedmatch with no problem at all but I understand it > > allows for more variations in the raw data. > > > > > > > > The header on the Ancestry data I have is as follows: > > > > > > > > #AncestryDNA raw data download > > > > #This file was generated by AncestryDNA at: 10/07/2017 01:20:13 UTC > > > > #Data was collected using AncestryDNA array version: V2.0 > > > > #Data is formatted using AncestryDNA converter version: V1.0 > > > > #Below is a text version of your DNA file from Ancestry.com DNA, LLC. > THIS > > > > #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL > > RESEARCH > > > > #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. > > THE > > EXPORTED DATA IS > > > > #SUBJECT TO THE AncestryDNA TERMS AND CONDITIONS, BUT PLEASE BE AWARE > THAT > > THE > > > > #DOWNLOADED DATA WILL NO LONGER BE PROTECTED BY OUR SECURITY MEASURES. > > > > #WHEN YOU DOWNLOAD YOUR RAW DNA DATA, YOU ASSUME ALL RISK OF STORING, > > > > #SECURING AND PROTECTING YOUR DATA. FOR MORE INFORMATION, SEE > ANCESTRYDNA > > FAQS. > > > > # > > > > #Genetic data is provided below as five TAB delimited columns. Each line > > > > #corresponds to a SNP. Column one provides the SNP identifier (rsID > where > > > > #possible). Columns two and three contain the chromosome and basepair > > position > > > > #of the SNP using human reference build 37.1 coordinates. Columns four > and > > five > > > > #contain the two alleles observed at this SNP (genotype). The genotype > is > > reported > > > > #on the forward (+) strand with respect to the human reference. > > > > rsid chromosome position allele1 allele2 > > > > > > > > I am not a tekkie and just want to get on Family Tree DNA. Can anyone > help > > me with this? > > > > > > > > Thank you so much! > > > > > > > > Alice > > > > > > > > > > > > > > > > ------------------------------ > > > > Message: 3 > > Date: Sun, 8 Oct 2017 15:41:39 -0500 > > From: Nancy Custer <[email protected]> > > To: <[email protected]> > > Subject: Re: [DNA] Ancestry upload to Family Tree DNA - problem > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset="utf-8" > > > > You will need the zipped file for upload not the txt file. Some browsers > > will unzip your file and put the txt file in your download folder and the > > original zip file in the trash. > > > > Look in your trash file for the zipped file and choose that for upload to > > FTDNA. Of course, move the zipped file out of the trash first?? > > > > If you don't find the zip file in your trash folder, you can set your > > browser not to open/unzip files on download. Then download again. In > > Safari, that option is under Preferences in the first screen. I leave > mine > > set that way all the time. > > > > Sent from my iPhone > > > > > On Oct 8, 2017, at 3:02 PM, Genealice <[email protected]> > > wrote: > > > > > > Hi, > > > > > > > > > > > > OK, I fully admit I joined this list because a problem has cropped up > and > > > I'm posting straightaway. But I hope it will be of interest to the > > mailing > > > list and thank you for having me! > > > > > > > > > > > > I am trying to do an autosomal transfer, uploading an Ancestry.com raw > > data > > > file to Family Tree DNA. However I keep on getting the following > message > > > > > > > > > > > > "The specified file 'Ancestry dna.txt' could not be uploaded. The file > > is an > > > unsupported version or in a corrupt/malformed format. Please place an > > order > > > for Family Finder <https://www.familytreedna. > com/products/family-finder> > > or > > > download the file and try again." > > > > > > > > > > > > Looking on the FTDNA message boards this seems to be a common problem. > > There > > > seem to a number of different theories over this: that is on FTDNA's > > side. > > > That it is Ancestry.com and the files are smaller than they should be. > > That > > > it is to do with the header. I have tried replacing the header with > that > > > suggested on the message board but it made no difference. > > > > > > > > > > > > I have posted it on Gedmatch with no problem at all but I understand it > > > allows for more variations in the raw data. > > > > > > > > > > > > The header on the Ancestry data I have is as follows: > > > > > > > > > > > > #AncestryDNA raw data download > > > > > > #This file was generated by AncestryDNA at: 10/07/2017 01:20:13 UTC > > > > > > #Data was collected using AncestryDNA array version: V2.0 > > > > > > #Data is formatted using AncestryDNA converter version: V1.0 > > > > > > #Below is a text version of your DNA file from Ancestry.com DNA, LLC. > > THIS > > > > > > #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL > > > RESEARCH > > > > > > #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. > > THE > > > EXPORTED DATA IS > > > > > > #SUBJECT TO THE AncestryDNA TERMS AND CONDITIONS, BUT PLEASE BE AWARE > > THAT > > > THE > > > > > > #DOWNLOADED DATA WILL NO LONGER BE PROTECTED BY OUR SECURITY MEASURES. > > > > > > #WHEN YOU DOWNLOAD YOUR RAW DNA DATA, YOU ASSUME ALL RISK OF STORING, > > > > > > #SECURING AND PROTECTING YOUR DATA. FOR MORE INFORMATION, SEE > > ANCESTRYDNA > > > FAQS. > > > > > > # > > > > > > #Genetic data is provided below as five TAB delimited columns. Each > line > > > > > > #corresponds to a SNP. Column one provides the SNP identifier (rsID > > where > > > > > > #possible). Columns two and three contain the chromosome and basepair > > > position > > > > > > #of the SNP using human reference build 37.1 coordinates. Columns four > > and > > > five > > > > > > #contain the two alleles observed at this SNP (genotype). The genotype > > is > > > reported > > > > > > #on the forward (+) strand with respect to the human reference. > > > > > > rsid chromosome position allele1 allele2 > > > > > > > > > > > > I am not a tekkie and just want to get on Family Tree DNA. Can anyone > > help > > > me with this? > > > > > > > > > > > > Thank you so much! > > > > > > > > > > > > Alice > > > > > > > > > > > > > > > > > > > > > ------------------------------- > > > To unsubscribe from the list, please send an email to > > [email protected] with the word 'unsubscribe' without > > the quotes in the subject and the body of the message > > > > > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > To contact the GENEALOGY-DNA list administrator, send an email to > > [email protected] > > > > To post a message to the GENEALOGY-DNA mailing list, send an email to > > [email protected] > > > > __________________________________________________________ > > To unsubscribe from the list, please send an email to > > [email protected] > > with the word "unsubscribe" without the quotes in the subject and the > body > > of the > > email with no additional text. > > > > > > ------------------------------ > > > > End of GENEALOGY-DNA Digest, Vol 12, Issue 668 > > ********************************************** > > > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without > the quotes in the subject and the body of the message >