GEDCOM
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 requests 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
- Other wiki pages for GEDCOM
- Gramps and GEDCOM
- GEDCOM 7 support (future)
- Addon:GEDCOM Extensions addon exporter plugin (source code: addons-source/blob/master/GedcomExtensions/GedcomExtensions.py
- Lossless GEDCOM Export
- Import of foreign language GEDCOM
- Gramps Glossary term: GEDCOM
- Other genealogy tools
- Import from another genealogy program (GEDCOM dialects)
- Related source code
- gramps/plugins/lib/libgedcom.py - (custom tag section)
- gramps/plugins/importer/importgedcom.py
- gramps/plugins/export/exportgedcom.py
- GedcomExtensions.py addon
- Other reference pages for related file formats
- Gramps XML
- 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.