How to Use a GEDCOM Validator to Fix Genealogy Errors
GEDCOM Validator Checklist: Common Issues and How to Resolve Them
1) File format & encoding
- Problem: Wrong file extension or non-UTF-8/ANSI encoding causes import failures.
- Fix: Ensure file uses .ged extension and save as UTF-8 (or ANSI if required by target software). Replace or remove unknown byte-order marks (BOM).
2) Level numbers and tag structure
- Problem: Incorrect level numbers, missing tags, or tags at the wrong level (e.g., a 2-level tag directly under a 0-level).
- Fix: Validate that each line starts with a level number (0,1,2…), followed by a tag or cross-reference. Reorder or adjust levels so child tags are one level greater than their parent.
3) Required tags and mandatory data
- Problem: Missing required tags like INDI/NAME, FAM/HUSB/WIFE, or missing DATE for events.
- Fix: Add essential records and key tags. For individuals, include NAME and at least one event (BIRT/DEAT) with a DATE where possible.
4) Invalid or non-standard tags
- Problem: Use of proprietary or misspelled tags that other tools don’t recognize.
- Fix: Replace non-standard tags with standard GEDCOM tags (e.g., use BIRT instead of BIRTH) or move custom data into NOTE or custom tags prefixed with an underscore per GEDCOM spec.
5) Cross-reference and pointer issues
- Problem: Broken pointers (e.g., @I1@ referenced but no corresponding record) or duplicate IDs.
- Fix: Ensure every referenced ID exists and is unique. Renumber or regenerate IDs consistently.
6) Date formats and ambiguous dates
- Problem: Inconsistent or nonstandard date strings (e.g., “Spring 1900”, “03/04/05”) preventing parsing.
- Fix: Use GEDCOM-standard date formats (e.g., 04 APR 1905) or ISO-style where supported. Add DATE tags in event subrecords.
7) Place format inconsistencies
- Problem: Places written inconsistently (different spellings or order) cause duplicate place entries.
- Fix: Standardize places as “City, County, State, Country”. Use consistent spelling and consider a lookup/normalization step.
8) Character escaping and special characters
- Problem: Unescaped commas, slashes, or control characters break parsing.
- Fix: Escape or remove problematic characters; ensure multi-line values use CONT/CONC lines correctly per GEDCOM spec.
9) Long lines and line continuations
- Problem: Lines exceeding length limits getting truncated or broken.
- Fix Use CONC and CONT tags to split long values according to the GEDCOM specification.
10) Multimedia and external references
- Problem: Missing file paths, incorrect pointers to media objects, or unsupported media tags.
- Fix: Verify that multimedia file links exist and use proper OBJE records; include relative paths or ensure images are uploaded to target system.
11) Inconsistent family relationships
- Problem: Child listed in a family but not linked to parents, or spouse links mismatched.
- Fix: Ensure FAMC/FAMS pointers are reciprocal: individuals reference families and families reference individuals correctly.
12) Duplicate records and merged individuals
- Problem: Same person exists multiple times with slight variations.
- Fix: Use deduplication tools or manually merge records, preserving unique identifiers in notes. Keep a backup before merging.
13) Notes, sources_
Leave a Reply