#2443 update_isdead while Gedcom import


1 DEAT Sterbeurkunde
2 DATE 19 AUG 2007
2 PLAC Brügge, Lüdenscheid, Deutschland
4 LATI 51.209
4 LONG 7.570
2 SOUR @Q00001@

The above part of a Gedcom file has not let to an i_isdead = 1 content in the respective record of the individuals table while importing the Gedcom file.
Is this due to the Gedcom is not exactly V5.5 compliant

if (preg_match("/\d DATE.*\s(\d{3,4})\s/", $deathrec, $match)) {
return update_isdead($pid, get_id_from_gedcom($GEDCOM), $match[1] + $cyear < date("Y"));


  • Gerry Kroll

    Gerry Kroll - 2008-12-29

    It's probably because of the text on the 1 DEAT line. According to the GEDCOM 5.5 spec, it's supposed to be either "Y" or empty. PGV has extended this to include "N" as another legitimate value.

    Since it's neither "Y" nor empty, it must mean "N".

    Your text, which is actually a Source, could have been entered as a 2 NOTE.

  • Greg Roach

    Greg Roach - 2009-01-10

    IIRC, we have a similar problem with another user who likes to record "1 DEAT holocaust/2 DATE .../2 PLAC ...'

    My understanding of the spec (bottom of page 21 of the 5.5.1 spec) says that an event occurs if either:
    1) the value is "Y"
    2) there is a date or place.

    Thus this record should *NOT* assert a death.

    1 DEAT
    2 NOTE No death found in UK death indexes. Either he emmigrated or is over 97

    Fixed in SVN.

  • Greg Roach

    Greg Roach - 2009-01-10
    • assigned_to: nobody --> fisharebest
    • status: open --> pending-fixed
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 100 days (the time period specified by
    the administrator of this Tracker).

  • SourceForge Robot

    • status: pending-fixed --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks