Changes

{{stub}}

GRAMPS V2.x database (.grdb): Prior to Gramps Version 3.0, this native Gramps database format was a specific form of the Berkeley database (BSDDB) with a special structure of data tables. This format was binary and architecture-dependent. It was very quick and efficient, but not generally portable across computers with different binary architecture (e.g. i386 vs. alpha).

{{man warn|Import from the Gramps V2.x format is not supported by Gramps 6.0.|If you have an old V2.x database, then you must import it into Gramps V3.0.x, export it from there to Gramps XML (or Gramps XML Package), and then import it into Gramps 6.0.}}

To move your Gramps data from version 2.x to version 6.0.x you must import the v2.x database into an earlier Gramps v3.0.x program and then either save the database and import it into Gramps 6.0.x, or export the database in [[XML]] format from the earlier Gramps version and import it into Gramps 6.0.x.

{{-}}

The Gramps [[XML]] and Gramps [[XML]] Package database are the native Gramps formats. There is no risk of information loss when importing (restore) from or exporting to these formats.

If you import information from another Gramps database or Gramps [[XML]] database, you will see the progress of the operation in the progress bar of Gramps main window. When the import finishes, a feedback window shows the number of imported objects. If the imported data originates from the very family tree in which you import the data, the import feedback gives suggestions about what could be merged; the merge is '''not''' done automatically for you. If you want to merge basic genealogy data automatically, consider CSV Spreadsheet Export/Import.

The Gramps CSV Spreadsheet format allows importing and exporting of a subset of your Gramps data in a simple spreadsheet format. See [[Gramps 6.0 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information.

First create a [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|new empty Family Tree]]. Then select the menu {{man menu|Family Trees ->Import}} or the [[Gramps_6.0_Wiki_Manual_-_Keybindings#2|keybinding]] {{Man key press|CTRL|I}} then use the {{man label|[[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Import_Family_Tree_dialog|Import Family Tree]]}} dialog to select the GEDCOM file you want to import, depending on the type of GEDCOM you may then see the {{man label|[[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#GEDCOM_Encoding_dialog|GEDCOM Encoding]]}} dialog.

{{-}}

[[File:GEDCOM-Encoding-dialog-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} GEDCOM Encoding - dialog]]<!-- to recreate find and download or create an ANSI GEDCOM file as the Gramps ( sample.ged ) file does not show this dialog / minor issue/note: the word "Gramps - " is shown before the dialogs name instead of after it like other dialogs! -->

{{-}}

[[File:ImportStatistics-dialog-example-GrampXML-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Import Statistics - dialog - Showing results for "Example.gramps" the Gramps XML file]]

Shows details of the import statistics depending on the imported file type.

{{-}}

{{stub}}

[[File:GEDCOM-import-report-result-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} GEDCOM import report - example results.]]<!-- to recreate find a large non standard GEDCOM and import it! -->

{{-}}

[[File:Source-Note-GEDCOMImportNote-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} GEDCOM import note indicating omitted data attached to "Source>Note"(data from "GEDitCOM" - "GEDCOM 5.5 Torture Test Files")]]

{{-}}

<!-- move to it's own appendix | no need to get technical here -->

This section describes any GEDCOM data that cannot be directly represented in Gramps, and how it is handled. For additional information on the limits of GEDCOM imports (and exports), please read the section on [[Gramps and GEDCOM]].

Gramps has no direct representation of this data, and hence all information there has to be stored in other objects. Depending on a [[Gramps_6.0_Wiki_Manual_-_Settings#Source_GEDCOM_import|Import preferences]] setting, a 'default source' object may be created. If this is created, then much of the data is stored in that {{man label|Source}}, or in {{man label|Repositories}} attached to that source.

HEADER:=

The PLAC FORM is stored internally and used to govern the interpretation of places (in accordance with the GEDCOM specification).

The SUBMISSION_RECORD (there should be only one, but this is not checked) is stored as a {{man label|Data}} item of the 'default source'

+1 RIN <AUTOMATED_RECORD_ID> {0:1}

SUBMITTER_RECORDs (there may be more than one) are stored as {{man label|Repository}} records attached to the 'default source' except as indicated in bold below. The SUBMITTER_RECORD that corresponds with the SUBM record in the HEADER is used to set the [[Gramps_6.0_Wiki_Manual_-_Tools#Edit_Database_Owner_Information|database owner]] and can be copied to the [[Gramps_6.0_Wiki_Manual_-_Settings#Researcher|Researcher Information]] tab if required.

* RFN and RIN are ignored

The INDIVIDUAL_RECORD is stored as a Gramps {{man label|Person}} record, except as indicated in bold below.

* Individual attribute structure, type, date, place structure, address structure, age, agency, cause and multimedia link are all ignored.

The FAM_RECORD is stored as a Gramps {{man label|Family}} record.

* The REFN and REFN:TYPE are stored as {{man label|Attributes}} of the {{man label|Family}}, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.

The SOURCE_RECORD is stored as a Gramps {{man label|Source}} record, except as indicated in bold below.

* DATA and its subsidiary records are ignored

The REPOSITORY_RECORD is stored as a Gramps {{man label|Repository}} record, except as indicated in bold below.

* REFN, REFN:TYPE and RIN are ignored

The MULTIMEDIA_RECORD is stored as a Gramps {{man label|Media}} record, except as indicated in bold below.

* REFN, REFN:TYPE and RIN are ignored

The NOTE_RECORD is stored as a Gramps {{man label|Note}} record, except as indicated in bold below.