Difference between revisions of "GEDCOM"
(→See also) |
m (→Collections of GEDCOM extension tags used in different programs) |
||
(19 intermediate revisions by 4 users not shown) | |||
Line 2: | Line 2: | ||
==GEDCOM References== | ==GEDCOM References== | ||
− | * [http:// | + | * [https://gedcom.io/specs/ gedcom.io GEDCOM specification documents] (versions 7.0.1, 5.5.1, 5.5) |
− | * GEDCOM 5.5 ([http://www.familysearch.org/GEDCOM/GEDCOM55.EXE Envoy], [http://www.math.clemson.edu/~rsimms/genealogy/ll/gedcom55.pdf pdf], [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm html]) | + | * [http://wikipedia.org/wiki/GEDCOM GEDCOM] From Wikipedia |
− | * [http://pjcj.sytes.net/pjcj.net/html/perl.html#Gedcom.pm Gedcom.pm] | + | * GEDCOM 5.5 ([http://www.familysearch.org/GEDCOM/GEDCOM55.EXE Envoy], [http://www.math.clemson.edu/~rsimms/genealogy/ll/gedcom55.pdf pdf], [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm html]) |
− | * GEDCOM 5.5.1 draft ([http://www.phpgedview.net/ged551-5.pdf pdf]) | + | * [https://web.archive.org/web/20131224010411/http://pjcj.sytes.net/pjcj.net/html/perl.html#Gedcom.pm Gedcom.pm] [Internet archive capture: 24 Dec 2013] |
− | * GEDCOM | + | * GEDCOM 5.5.1 draft ([http://www.phpgedview.net/ged551-5.pdf pdf]) <small>2 October 1999</small> |
+ | * GEDCOM 5.5.1 ([https://edge.fscdn.org/assets/img/documents/ged551-5bac5e57fe88dd37df0e153d9c515335.pdf pdf]) <small>15 November 2019</small>, [https://www.familysearch.org/wiki/en/GEDCOM Final version released] with updated email, dates, and copyright. | ||
+ | * GEDCOM 5.5.5 <small>2 October 2019</small> [https://www.tamurajones.net/GEDCOM555JustARevision.xhtml Unsanctioned, copyright violation] | ||
+ | * GEDCOM 6.0 beta ([https://sourceforge.net/projects/gedcomfilter/files/GEDCOM%20XML%20Specification/GEDCOM%20XML%206.0%20Beta/GedXML60.pdf/download archived pdf]) - Note - this effort appears to have been abandoned and the PDF ([http://www.familysearch.org/GEDCOM/GedXML60.pdf http://www.familysearch.org/GEDCOM/GedXML60.pdf]) document link is invalid on the sponsoring FamilySearch website. | ||
==GEDCOM Testing== | ==GEDCOM Testing== | ||
Line 18: | Line 21: | ||
==Converting ANSEL to Unicode and back== | ==Converting ANSEL to Unicode and back== | ||
− | * | + | * Gramps exports and imports ANSEL GEDCOM, but not all codes are supported. Test the output on the character ? which is used if a character is not understood |
* Perl MARC::Charset module: Available on [http://search.cpan.org/~esummers/MARC-Charset-0.95/lib/MARC/Charset.pm cpan], and well supported . Can convert MARC8 to Unicode and back. As ANSEL is a subset of MARC8 (consisting of the (extended) latin characters) it will convert all ANSEL GEDCOMS to Unicode. (:arrow:) More info, and a script that can convert: see the attachment to bug {{bug|831}}. | * Perl MARC::Charset module: Available on [http://search.cpan.org/~esummers/MARC-Charset-0.95/lib/MARC/Charset.pm cpan], and well supported . Can convert MARC8 to Unicode and back. As ANSEL is a subset of MARC8 (consisting of the (extended) latin characters) it will convert all ANSEL GEDCOMS to Unicode. (:arrow:) More info, and a script that can convert: see the attachment to bug {{bug|831}}. | ||
* [http://marc4j.tigris.org/ marc4j] - Java implementation of a convertor, also MARC8 to Unicode. Unclear if it converts correctly combined unicode characters. | * [http://marc4j.tigris.org/ marc4j] - Java implementation of a convertor, also MARC8 to Unicode. Unclear if it converts correctly combined unicode characters. | ||
Line 35: | Line 38: | ||
==See also== | ==See also== | ||
− | * [[ | + | |
− | * [ | + | ;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 | ||
+ | * [[GEDCOM 7 support]] | ||
+ | |||
+ | * [[Gramps_and_GEDCOM]] | ||
+ | * [[Gramps XML]] | ||
+ | * [https://gramps.discourse.group/t/best-way-to-integrate-foreign-gedcom/157/2 Import of foreign language GEDCOM] | ||
* [[Gramps and GEDCOM]] | * [[Gramps and GEDCOM]] | ||
− | * [[GEDCOM Extensions]] | + | * [[Addon:GEDCOM Extensions]] exporter plugin (source code: [https://github.com/gramps-project/addons-source/blob/master/GedcomExtensions/GedcomExtensions.py addons-source/blob/master/GedcomExtensions/GedcomExtensions.py] |
+ | * [[Lossless GEDCOM Export]] | ||
+ | * [[Other_genealogy_tools#Gedcom_one-to-one_to_XML|ged1212xml]] | ||
+ | * [https://osdn.net/projects/sfnet_gedcomfilter/ GEDCOM Import/Export-Filter] project on ODSN (Open Source Development Network) | ||
+ | |||
+ | |||
+ | === Collections of GEDCOM extension tags used in different programs === | ||
+ | * [[Import from another genealogy program]] (GEDCOM dialects) | ||
+ | * [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.) | ||
+ | * [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#GEDCOM_import|Manage Family Trees - GEDCOM import]] | ||
+ | * [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/FamilySearch/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. | ||
+ | |||
+ | * [https://www.linkedin.com/in/dallan-quass-7059/ Dallan Quass] GitHub [https://github.com/DallanQ/Gedcom GEDCOM repository] incudes the [https://github.com/DallanQ/Gedcom/wiki/Demo demo]. ''GEDCOM -> model -> json -> model -> GEDCOM'' round-trip shows the GEDCOM tags that are represented in the model as extensions, and tags that cannot be represented. | ||
+ | ;* [https://github.com/DallanQ/Gedcom/wiki/Specification-differences Specification] differences between the object model and the GEDCOM 5.5 Specification. | ||
+ | ;* set of [https://github.com/DallanQ/Gedcom/wiki/UML-Diagrams UML diagrams] illustrating the core GEDCOM class and each of the top-level objects. | ||
[[Category:Developers/Reference]] | [[Category:Developers/Reference]] | ||
[[Category:Developers/General]] | [[Category:Developers/General]] | ||
+ | [[Category:Documentation]] |
Latest revision as of 07:23, 2 December 2023
GEDCOM stands for Genealogical Data Communications and is a file format specification developed by the Family and Church History Department of The Church of Jesus Christ of Latter-day Saints. It allows different genealogical software programs to share data with each other.
Contents
GEDCOM References
- gedcom.io GEDCOM specification documents (versions 7.0.1, 5.5.1, 5.5)
- GEDCOM From Wikipedia
- GEDCOM 5.5 (Envoy, pdf, html)
- Gedcom.pm [Internet archive capture: 24 Dec 2013]
- GEDCOM 5.5.1 draft (pdf) 2 October 1999
- GEDCOM 5.5.1 (pdf) 15 November 2019, Final version released with updated email, dates, and copyright.
- GEDCOM 5.5.5 2 October 2019 Unsanctioned, copyright violation
- GEDCOM 6.0 beta (archived pdf) - Note - this effort appears to have been abandoned and the PDF (http://www.familysearch.org/GEDCOM/GedXML60.pdf) document link is invalid on the sponsoring FamilySearch website.
GEDCOM Testing
- Gedcom.pm
- gedchk (perl), gedchk.exe
- GEDitCOM "Torture Test" files
- ANSEL and Unicode GEDCOM sample files
- Calico Pie's GEDCOM Coverage Test
- VGed (Windows OS)
- Gedcom Validation by Tamura Jones.
Converting ANSEL to Unicode and back
- Gramps exports and imports ANSEL GEDCOM, but not all codes are supported. Test the output on the character ? which is used if a character is not understood
- Perl MARC::Charset module: Available on cpan, and well supported . Can convert MARC8 to Unicode and back. As ANSEL is a subset of MARC8 (consisting of the (extended) latin characters) it will convert all ANSEL GEDCOMS to Unicode. (:arrow:) More info, and a script that can convert: see the attachment to bug 831.
- marc4j - Java implementation of a convertor, also MARC8 to Unicode. Unclear if it converts correctly combined unicode characters.
ANSEL/MARC References
- ANSI/NISO Z39.47-1993(R2002)
- Library of Congress, MARC specification tables
- MARC proposal 2006-09, Lossless technique for conversion of Unicode to MARC-8
- MARC proposal 2006-04, Technique for conversion of Unicode to MARC-8
Unofficial ANSEL to Unicode conversion lists
These cover the original ANSEL spec, now preseded by MARC8.
- ANSEL to Unicode by Thomas Berger
- ANSEL to Unicode by Heiner Eichmann
- Latin Characters in Unicode and ANSEL
See also
- Current open Feature request for Gramps
- 6023 Export Family Historian GEDCOM Extensions
- 688 Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)
- 9249 GEDCOM import improvements to support Ancestry.com, FTM 2012/2014 and FTM for MAC 3
- GEDCOM 7 support
- Gramps_and_GEDCOM
- Gramps XML
- Import of foreign language GEDCOM
- Gramps and GEDCOM
- Addon:GEDCOM Extensions exporter plugin (source code: addons-source/blob/master/GedcomExtensions/GedcomExtensions.py
- Lossless GEDCOM Export
- ged1212xml
- GEDCOM Import/Export-Filter project on ODSN (Open Source Development Network)
Collections of GEDCOM extension tags used in different programs
- Import from another genealogy program (GEDCOM dialects)
- 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.)
- Manage Family Trees - GEDCOM import
- GEDCOM Extension List (FHUG Knowledge Base), GEDCOM custom tags used by Family Historian
- GEDCOM Files - Custom tags in Legacy Family Tree
- (German)Collection of GEDCOM extension tags used in different programs
Others projects
- 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.
- Dallan Quass GitHub GEDCOM repository incudes the demo. GEDCOM -> model -> json -> model -> GEDCOM round-trip shows the GEDCOM tags that are represented in the model as extensions, and tags that cannot be represented.
- Specification differences between the object model and the GEDCOM 5.5 Specification.
- set of UML diagrams illustrating the core GEDCOM class and each of the top-level objects.