Changes

= Export This Addon has a collection of unofficial GEDCOM Extensions =extensions which extend Gramps GedcomWriter to include common non-compliant GEDCOM additions.

There is an Addon (available for Gramps 4.0 and higher) which has a collection of unofficial GEDCOM extensions which extend Gramps GedcomWriter to include common non-compliant GEDCOM additions. If the feature you want is not listed below, then you can either add it yourself, or ask a developer to help you.

The code is in the Addon [https://github.com/gramps{{-project/addons-source/blob/master/GedcomExtensions/GedcomExtensions.py addons-source/blob/master/GedcomExtensions/GedcomExtensions.py].}}

== Export GEDCOM Extensions ==

The code currently supports the following extensionsGEDCOM Extensions are supported:

== Running the Exporter Usage ==

[[File:GEDCOMExtensions-GED2-ExportOptions-tab-ExportAssistant-50.png|right|450px|Checkbox enabled for "Include witnesses" associated with a family event.]] To run the exporter, select {{man menu|Family Trees > Export..}}, press {{man button|Next}}, on the {{man label|Choose the output format}} dialog select {{man label|"Gedcom GEDCOM Extensions(GED2)"}}, press {{man button|Next}}. Select On the {{man label|Export options}} dialog select the relevant optionsGEDCOM extension option:* {{checkbox|1}} {{man label|Include witnesses}} - (checked by default) Exports witnesses associated with a family event* {{checkbox|1}} {{man label|Include media}} - (checked by default) Then press {{man button|Next}}, and after selecting the save location and applying the export the data should be exported to a file with the extension ".ged2". Afterwards, you can change the extension from ".ged2" to ".ged" and treat as a normal GEDCOM file.

= Import Gedcom GEDCOM Extensions =

See feature request:* {{bug|10550}} '''Refactor Gramps GEDCOM import so as to support GEDCOM extension addons''' = See also =The code is available from [https://github.com/gramps-project/addons-source/blob/master/GedcomExtensions/GedcomExtensions.py addons-source/blob/master/GedcomExtensions/GedcomExtensions.py]. ;Current open Feature request for Gramps:* {{bug|6023}} Export Family Historian GEDCOM Extensions* {{bug|688}} Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)* {{bug|9249}} GEDCOM import improvements to support Ancestry.com, FTM 2012/2014 and FTM for MAC 3 * [[Gramps_and_GEDCOM]] == Collection of GEDCOM extension tags used in different programs ==* [http://genealogytools.com/family-tree-maker-to-gedcom-to-other-apps-crosswalk/ Family Tree Maker to GEDCOM to Other Apps Crosswalk], by Keith Riggle (This spreadsheet shows alot of the custom GEDCOM extension tags for a number of programs.)* [http://www.fhug.org.uk/wiki/doku.php?id=glossary:gedcom_extension_list GEDCOM Extension List (FHUG Knowledge Base)], GEDCOM custom tags used by Family Historian* [http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html GEDCOM Files] - Custom tags in Legacy Family Tree* (German)[http://wiki-de.genealogy.net/GEDCOM/_Nutzerdef-Tag#.C3.9Cbersicht_bekannter_Nutzerdefinierter_Kennzeichen Collection of GEDCOM extension tags used in different programs] == Others projects ==

* [https://github.com/DallanQFamilySearch/Gedcom Gedcom GEDCOM (WeRelate.org)] is a project for parsing objects ignored by a model. It includes classes and attributes for every GEDCOM tag sequence appearing in more than 4% of the 7000 GEDCOMs submitted to WeRelate.org over the past five years, with the exception of four software-specific schema tags: SCHEMA, _EVENT_DEFN, _PLAC_DEFN, and _EVDEF, generated by Family Tree Maker, Personal Ancestral File, Legacy, and RootsMagic respectively.

** set of UML diagrams illustrating the core Gedcom GEDCOM class and each of the top-level objects.[https://github.com/DallanQ/Gedcom/wiki/UML-Diagrams]