My Ahnentafel to GEDCOM converter, Ahnen2GED, apparently has more uses than I realized. It was initially written to convert the output of DNArboretum (a tool to create ahnentafels from Family Tree DNA trees) to a GEDCOM, but many people are using it to convert other text files as well. So I have enhanced Ahnen2GED to accept any date format that ends with a space followed by the four digit year, so for example 10 jan 1920. I also fixed the known problem where it did not work properly if the lines for the grandparents were not there.
The URL for my Ahnentafel to GEDCOM converter is:
Below is the documentation of the format Ahen2GED expects. Hopefully this will help you create text files that will easily convert to GEDCOMs using my tool. Especially DNAgedcom.com users!
Look at the image above of the format Ahnen2GED expects as output from DNArboretum. Each line must start with the ahnentafel number followed by a period, a space, or a tab. Then a space and the person’s name. Then the word “born:” with a colon followed by a space then the birth location which can include commas or be blank. Finally a comma followed by the date the person was born on which can be either just the year, or else any other date format as long as it ends with a space and then the four digit year with no commas. Thus legal dates are 1 dec 2004 or abt. 1909 but not Apr 19, 2004 (has a comma) or 12/12/1914 (no space before the year). Finally the word “died:” followed by the place and date of death where the same formatting rules apply as for born.
My informant told me that he uses the DNAgedcom.com client tool (a paid feature under the subscribers tab) to download tree information to a spreadsheet from his matches at Ancestry.com DNA. He then massages the file, which has the ahnentafel numbers already, into a text file for my tool so that he can use the GEDCOM compare tool, also at DNAgedcom. He was curious if I could add the ability to my tool to do that massaging. “Probably,” I said. “I would have to see some samples.”
Are there other users out there who want this capability? How about more date formats like 02-02-1899 or 1/6/1976? If so pass the hat, once I have at least six glasses of wine (click button in right hand column), I will write it.
UPDATE 27 May 2018: Ahnen2GEDcom will now put slashes on both sides of the surname if that box is checked making it usable with DNAgedcom’s gedcom upload capability. Also it works fine with the chrome add-on pedigee thief which creates ahentafel lists from Ancestry and MyHeritage trees in the pedigree view.
UPDATE 20 Oct 2018: Mac users can have problems because the line endings from Mac text files are not compatible with PC line endings. The solution to this problem is for Mac users to create the ahnentafel using Google docs and save from there as a text file or use the BBedit editor.