GEDCOM

The technical section

Moderator: Global Moderators

DavidWW
Posts: 5057
Joined: Sat Dec 11, 2004 9:47 pm

GEDCOM

Post by DavidWW » Tue Feb 01, 2005 11:02 am

GEDCOM is a tool for transferring data between different genealogy software packages. It's not a very good idea to consider using a package that doesn't have the facility to create and import GEDCOM files.

GEDCOM is an acronym for GEnealogy Data COMmunication. It is the name used for a special text file format developed by the projects and planning division of the Church of Jesus Christ of Latter-day Saints. This format was developed so that a common standard of communication could exist between the Church and submitters of genealogical data. This has now evolved into the defacto standard for data exchange between most genealogy software programs and systems.

It's probable that the current version of GEDCOM will be replaced quite soon by a new standard based on the XML software, - see Dick Eastman's article at http://www.ancestry.com/learn/library/a ... ticle=3396

While creating this post I came across the set of utilities at http://www.rootsweb.com/~gumby/ged.html which allow the more technically orientated to manipulate GEDCOM files. I've never used these, but would hope that the fact that they are to be found on a RootsWeb site means that they are reasonable. But if you ever decided to do that then please, please backup the original GEDCOM file first.

In fact always, but always backup your data files first before you produce a GEDCOM file, and never ever, import a GEDCOM file into your main data files. Always first create a new set of data files.

A bit more info about the background and a more detailed explanation of GEDCOM files can be found at many places on the www by a quick Google, including http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp and
http://www.tedpack.org/gedwhat.html Note that I'm not suggesting that these are the best sites out there, just a couple of reasonable looking ones that were on the first page of my Google :!:

The following site goes into great technical detail http://www.genserv.com/gs/genged1.htm

As many of you will only be interested in the simple practicalities of creating and importing GEDCOM files AnnetteR very kindly contributed the following:

QUOTE
When wanting to transfer a GED.COM file from one software package to another this is how I do it. Go into to the software package where the file you want to transfer lives. Open the file and click on file on top left hand corner and the drop down menu should give an option saying Import/Export. From that option select export gedcom file. You should be given a choice of where to save the gedcom file on your C drive e.g., my documents etc or to floppy disc on the A drive. Depending on what package is being used it might be better to save to floppy but it is really down to choice.

To transfer this file to the new software package you should open a new family file and name it appropriately. Repeat the above in the new software package with the new file open but this time choose the Import option. Some software packages (like Legacy) have an Import wizard which makes it easy peezy and finds all the gedcom files on your C drive and it is just a case of clicking on the file you want and following the instructions. If there is no wizard just find the gedcom file you want to import from wherever you saved it on your C drive, or if saved to a floppy then insert the floppy into the A drive, and import it from there again following the instructions on screen.

If I can do it, it must be simple. :o
ENDQUOTE

Finally just a reminder about always creating backups of your data files before you do anything like this :roll:

Davie

PS Added later. I meant to add that while there's not often a problem when importing a GEDCOM file in terms of the main info, there can be glitches casued by date format, honorifics e.g. "Dr", terms such as Jnr, and the ability of the particular GEDCOM version to handle comments, and of the programme that you are using to handle comments in a GEDCOM.
Last edited by DavidWW on Wed Feb 02, 2005 9:14 am, edited 1 time in total.

StewL
Posts: 1396
Joined: Sat Dec 11, 2004 12:59 am
Location: Perth Western Australia

Post by StewL » Wed Feb 02, 2005 2:17 am

Wise word Davie, wise words.

When I first started on this torturous game of genealogy, I thought I was the bees knees when I imported a Gedcom file into a new family history programme I was using. I had already inputed a great deal of data into the programme manually. Well what happened you might ask? I ended up with a family history programme that duplicated almost every entry :oops:
In the end I had to delete the whole thing and start again. Now as Davie said, I have backups of each family Gedcom I have exported to my brothers and sister. Plus of course the main source Gedcom of my family. All saved under different names, placed in a special folder, and saved to CD.
Stewie

Searching for: Anderson, Balks, Barton, Courtney, Davidson, Downie, Dunlop, Edward, Flucker, Galloway, Graham, Guthrie, Higgins, Laurie, Mathieson, McLean, McLuckie, Miln, Nielson, Payne, Phillips, Porterfield, Stewart, Watson

Dz

GEDcom editing...

Post by Dz » Wed Feb 02, 2005 8:00 am

Windows notepad works for me! (Smaller GED files, through about 300-500 names. Microsoft's EDIT.exe works for larger ones.)

GEDcom files are, after all, nothing but plain text - and simple changes are MUCH quicker and easier than doing so in some huge, slow family tree program. (e.g. - correcting a misspelled name or one or two wrong dates.) Just don't mess with the first two elements in any line: a digit and a data tag indicating the "type" of info contained in that line. (e.g. - BIRT, PLAC, DEAT, etc.)

Along with the good links already provided in this thread, I'd like to add:
http://freepages.genealogy.rootsweb.com ... dView.html which is a great little (and FREE) GED viewer for windows. The author also provides a link for a Mac program that does much the same thing (though I haven't tried the Apple program...).

GEDview can save you a lot of time and trouble if you inspect a "foreign" GED file with it <I>before</I> importing it into your main genealogical program. If the GED doesn't work well with GEDview, you might not want to import it into your main program.
GEDView will quickly and compactly show the names, dates, relationships, etc. contained in the GED, but doesn't draw trees or (most importantly) do changes to ANY data. It doesn't WRITE any files at all - so it is very safe to use.

.

wini
Posts: 678
Joined: Sun Dec 25, 2005 2:39 pm
Location: West Australia

GEDCOM

Post by wini » Thu Dec 29, 2005 12:56 am

Please cancel my last post . I have browsed further down and found david's explanation of 1st February 2005

wini
Munro, McPhee, Gunn, Reid, McCreadie, Jackson, Cree, McFarland,Gillies,Gebbie,McCallum,Dawson
Glasgow, Durness,Kilmuir via Uig, Logie Easter
Old Monkland