Difference between revisions of "Import from another genealogy program"

From Gramps
Jump to: navigation, search
Line 63: Line 63:
 
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.
 
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.
  
* [[Media:fix_Ances_repo.py.gz | fix_Ances_repo.py.gz]] .. script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.
+
* [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] .. script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.
  
* [[Media:fix_Ances_map.py.gz | fix_Ances_map.py.gz]] .. script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.
+
* [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] .. script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.
  
* [[Media:fix_Ances_x1.py.gz | fix_Ances_x1.py.gz]] .. script to fix various non-standard gedcom usage or gedcom extensions, by converting the otherwise unusable data into a special NOTE entry like:
+
* [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] .. script to fix various non-standard gedcom usage or gedcom extensions, by converting the otherwise unusable data into a special NOTE entry like:
 
   2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111
 
   2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111
  

Revision as of 04:16, 1 January 2008


There are several ways to import your family tree into GRAMPS from another program. The best way depends on what program you want to copy the information from.

GRAMPS to GRAMPS

This is the easy one. The simplest and safest method to move all your information from one GRAMPS program to another on a different computer is to choose File -> Export from the first GRAMPS. Follow the instructions, choosing GRAMPS Package for the format to save.

Copy the file created by GRAMPS to the destination computer. Then in its GRAMPS, choose File -> Import and select the transferred file.

Standard GEDCOM as transfer tool

Most programs for family history can export and import GEDCOM (.ged) files.

  1. Check the documentation for your program to learn how to create a GEDCOM file with all your data.
    • If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
  2. In GRAMPS, choose File -> Import
  3. Locate the GEDCOM file created by your program, and choose Open.
Gnome-important.png
Check The Results

Check your data carefully once imported into GRAMPS. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. GRAMPS does its best to do the right thing with non-standard GEDCOM files, but it can't possibly cope with everything.


Take special attention that your media files are transferred too, and found by GRAMPS. In the menu Tools -> Utilities , you will find the Media Manager, with which you can change the path of your media objects to the new path if needed.

Import instructions from different programs

The Master Genealogist (TMG)

You have two options.

GEDCOM

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

  1. Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
    • TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
    • Write down which choices you make.
  2. Follow the instructions above for Standard GEDCOM.

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

tmg2gramps

For many people, using GEDCOM will lose too much information. If this is the case for you, you might like to try tmg2gramps, though it is aimed at advanced users.


Family Tree Maker

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into GRAMPS. Follow the instructions above for Standard GEDCOM.

Geneweb

GRAMPS can directly import from Geneweb. Choose File -> Import , select your Geneweb database and choose Open.

Ancestrologie

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

Programs for fixing some of the known problems

Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

  • fix_Ances_repo.py.gz .. script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.
  • fix_Ances_map.py.gz .. script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.
  • fix_Ances_x1.py.gz .. script to fix various non-standard gedcom usage or gedcom extensions, by converting the otherwise unusable data into a special NOTE entry like:
 2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines. The non-standard elements converted to APPX notes include:

* _ANCES_CLE_FIXE .. possibly something like REFN
* _ANCES_ORDRE .. unknown semantics
* _ANCES_XACTE .. (same) 
* _ANCES_XINSEE .. INSEE geographical code (evidently simplified 5-digit)
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record
* EVEN I .. (same)
* LIEU .. seems to add to existing PLAC data in an EVEN

Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.

Please also feel free to provide feedback on broken scripts or incorrect fixes