PyPedal is capable of importing from, and exporting to, GEDCOM 5.5 files using a subset
of data record and tag types from the standard (Table
Most of the information that can be
exchanged in GEDCOM files has no direct use in PyPedal, so important information from PyPedal's point-of-view is not lost. However, it's important to note that PyPedal's GEDCOM import and export is lossy! This means that information in a GEDCOM file is lost when importing the file, and data from PyPedal pedigrees is lost when exporting. There are many free and commercial packages for doing human genealogy that take full advantage of GEDCOM, so you might want to look at one if you need more advanced GEDCOM support than PyPedal provides.
B. GEDCOM File Handling
The list of recognized tags is hard-coded in a list named known_tags in pyp_io.load_from_gedcom().
GEDCOM 5.5 data records and tags imported by PyPedal.
Data Record Type & Supported Tags & DescriptionB.1
Some tags have slightly different connotatios in PyPedal than in GEDCOM. For example, in human genealogy marriages are important events, but that is not the case in animal pedigrees. PyPedal creates family records only for unique mating pairs, and marriage information is lost when importing a GEDCOM file. Similarly, no marriage information is exported, and you will not see any family records containing only HUSB and WIFE tags. Founders (animals with both parents unknown) will have individual records but no family records. The default birth year used by PyPedal is 1900; if you do not override that value then individuals with birth years of 1900 will not have BIRT/DATE tags written to their individual record. The same is true of default birth dates (01011900).
GEDCOM 5.5 data records and tags exported by PyPedal.
Data Record Type & Supported Tags & DescriptionB.2
Importation is done by reading the GEDCOM file, parsing out the supported tags into ``family'' and ``individual'', and using Python dictionaries (hash tables) to map everything down to individual records. Those individual records are then written to a file, the pedigree format string and pedfile variables are updated for the new file. That file is then loaded automatically. The downside is that you end up with two copies of each pedigree file, but disc space is cheap. I won't add an option for automatic deletion of the original GEDCOM file becuase of the lossiness of the import procedure.
The export process is uncoupled from the import process. You can export any pedigree
that PyPedal can read as a GEDCOM file regardless of the original source. Perhaps
some human types will be interested in some of the calculations that PyPedal can do,
or perhaps a dog breeder will do something unexpected, such as exporting to GEDCOM so
that they can use GRAMPS or something like that to manipulate their data. Who knows. Anyway, PyPedal supports two-way data flow.
See About this document... for information on suggesting changes.
- ... Description
- ... Description