Add autosomal DNA match list data to GEDCOM

I recently started a discussion in the FamilySearch GEDCOM github regarding adding autosomal DNA match list info to GEDCOM. Your participation in the discussion would be greatly appreciated. see: Add autosomal DNA match list data to GEDCOM. · FamilySearch/GEDCOM · Discussion #464 · GitHub

Thanks,
Ron Tilby

1 Like

Your proposal could possibly be implemented in Gramps by adding another table with the following fields:

  • Handle
  • Person reference 1
  • Person reference 2
  • Data Provider (Ancestry, 23andMe, GEDMatch, MyHeritage, Other)
  • Shared cM
  • Percent Shared
  • Number of Shared Segments
  • Unweighted Shared cM
  • Longest Segment cM

It would need a corresponding view and editor.

Does it really need that?

The data is already being used in Gramps with the Association and a CSV note. It isnt as flexible as it could be though.

Perhaps it could use a Source for each service with a crosswalk? We could share a source for each DNA service that leverage the dtd and schema doctype declarations as Notes?

Luther does suggest that using the ASSO tag as an alternative option. His initial design makes a lot of sense to me though.

I’d be interested to get other people’s views though.

I did use the DNA functions of GRAMPS but abandoned them there is too small of pool of data available at the chromosome level too make it worhtwhile
Attributes DNA a


.
I store all the date I need as Attributes of the person
See images a and b
a) is the normal DNA data relationship with an individual
b) because I have access to a number of “cousins” DNA on Ancestry there are a number of cousins that have a DNA link but not to me although they are on my tree correctly hence the shared aspect.
All these Attributes are permanently in my collections clipboard.
Note also 1st DNA Match to allows me to use the same format for another DNA test which I manage of a related person.
phil

1 Like

I have done a fair amount of data entry for DNA info into gramps. After a few false-starts, I ended up as follows:

Person Attributes

  • AncestryID (the Ancestry ID)
  • DNAkit (the GEDmatch kit number)
  • FTDNAkit (the FTDNA kit number)
  • Y-DNA Haplogroup
  • mtDNA Haplogroup

Association

For each match found in any of the services (Ancestry, FTDNA, GEDmatch, …) I add an Association. The Association is of type DNA and has a Note and a Source. The Source is the company that did the match and the Note contains the match info, as follows:

  • Ancestry - overall cM
  • FTDNA - segment list
  • GEDmatch - segment list

With this info, I can use the DNA Segment Map gramplet to display the map (useful for FTDNA and GEDmatch but not Ancestry).

I have also written reports with all of the DNA match info with their relationship for review.

I have over 150 people with Ancestry ID attributes. And over 50 Associations with segment-level details.

I found that putting match info as Person Attributes did not scale and caused confusion interpreting.

1 Like

I guess there are numerous ways of using/exploring this information. But
unless and until Ancestry open up with segment maps and hopefully auto
clustering then the rest are just bit players in this field I notice
LivingDNA is now doing segment maps showing shared segments but as they
still do not do trees you are relying on spotting a name
The one good thing I can say about Ancestry’s ThruLines project is the
visual appeal of the format even though many of the suggestions are wrong.
I am nearly there with my version of this with numerous false starts but
having all the DNA matches with links on common ancestors in graphical
form certainly makes looking for the rogues easier.
phil