Places - Place

This page describes a set of tests included in version 1.05 of the GEDCOM file assess.ged (download - view). Details change between versions.

Area Summary

People with the surname "Place" have events with PLAC and/or ADDR subrecords to test the place import capabilities of the target application.

Most target applications will import PLAC subrecords on events. Some will import both PLAC and ADDR subrecords on events. Several target applications I tested do not import ADDR subrecords on events.

This area also includes tests for the PHON, EMAIL, EMAI, and WWW records. The GEDCOM 5.5.1 specification includes them in the <ADDRESS_STRUCTURE> and indicates they may only be included if an ADDR record is included even though they are not subrecords of the ADDR record .

01-Latitude Longitude

This person has a BIRT event where the place is "Washington, DC" at N38.88923,W77.05020. The test is intended to determine if the target application recognizes latitude/longitude coordinates when importing places.

N38.88923,W77.05020 is a point near the Lincoln Monument in Washington, D.C.

Test Result Criteria

1 BIRT
2 DATE 1900
2 PLAC Washington, DC
3 MAP
4 LATI N38.88923
4 LONG W77.05020

02-Place Note

This person has a BIRT event where the place is "Philadelphia, PA" and the PLAC record has a NOTE value "Note for Philadelphia, PA". The test is intended to determine if the target application recognizes notes when importing places.

Test Result Criteria

1 BIRT
2 DATE 1900
2 PLAC Philadelphia, PA
3 NOTE Note for Philadelphia, PA

03-Place Exhibit

This person has a BIRT event where the place is "Philadelphia, PA" and has an exhibit. Place exhibits are not supported by the GEDCOM 5.5.1 specification so the target application may reject or ignore the exhibit.

This test uses the linked exhibit method where an OBJE follows the parent record (a BIRT record in this example) and includes a reference to another OBJE record which occurs later in the document.

Test Result Criteria

Non-Standard Content

1 BIRT
2 DATE 1900
2 PLAC Philadelphia, PA
3 OBJE @O214@
0 @O214@ OBJE
1 FILE C:\GedcomAssessment\place-03.jpg
2 FORM JPG
2 TITL 03-Place Exhibit Title
1 NOTE 03-Place Exhibit Note

04-PLAC and ADDR

This person has a BIRT event where the PLAC value is "Chicago, IL" and the ADDR value is "Wrigley Field<newline>1060 W Addison St".

This test is intended to show whether the target application will load both the PLAC and ADDR values.

Test Result Criteria

1 BIRT
2 DATE 1900
2 PLAC Chicago, IL
2 ADDR Wrigley Field
3 CONT 1060 W Addison St

05-ADDR Label

This person has a BIRT event with an ADDR record that includes only CONT subrecords.

Test Result Criteria

1 BIRT
2 DATE 1900
2 ADDR Jane Smith
3 CONT Assessor's Dept
3 CONT 610 Main Street
3 CONT Waltham, Massachusetts 02452

06-ADDR Label and Fields

This person has a BIRT event with an ADDR record that includes an address in "label" form but also parsed into more specific subrecords.

Test Result Criteria

1 BIRT
2 DATE 1900
2 ADDR John Doe
3 CONT c/o City Hall
3 CONT 1000 Commonwealth Avenue
3 CONT Newton Centre, Massachusetts 02459 USA
3 ADR1 John Doe
3 ADR2 c/o City Hall
3 ADR3 1000 Commonwealth Avenue
3 CITY Newton Centre
3 STAE Massachusetts
3 POST 02459
3 CTRY USA

07-PHON

This person has an OCCU event with an ADDR subrecord followed by a PHON subrecord.

Test Result Criteria

1 OCCU Clerk
2 DATE 1900
2 ADDR Public Works Dept.
3 CONT 610 Main Street
3 CONT Waltham, Massachusetts 02452
3 ADR1 Public Works Dept.
3 ADR2 610 Main Street
3 CITY Waltham
3 STAE Massachusetts
3 POST 02452
2 PHON (617) 555-1234

08-EMAIL

This person has an OCCU event with an ADDR subrecord followed by an EMAIL subrecord.

GEDCOM 5.5 did not include the EMAIL subrecord, so target applications that read GEDCOM 5.5.1 files as if they were GEDCOM 5.5 files may reject or ignore the subrecord.

Test Result Criteria

1 OCCU Clerk
2 DATE 1900
2 ADDR Mayor's Office
3 CONT 610 Main Street
3 CONT Waltham, Massachusetts 02452
3 ADR1 Mayor's Office
3 ADR2 610 Main Street
3 CITY Waltham
3 STAE Massachusetts
3 POST 02452
2 EMAIL dpw@@example.com

09-EMAI

This person has an OCCU event with an ADDR subrecord followed by an EMAI subrecord.

GEDCOM 5.5 did not include the EMAI subrecord, so target applications that read GEDCOM 5.5.1 files as if they were GEDCOM 5.5 files may reject or ignore the subrecord.

The GEDCOM 5.5.1 specification uses the tag EMAIL in one place (pg. 31) and the tag EMAI in another (pg. 87). This test and the last should expose whether the target application implemented one, the other, both, or none.

Test Result Criteria

Non-Standard Content

1 OCCU Clerk
2 DATE 1900
2 ADDR Zoning Dept.
3 CONT 610 Main Street
3 CONT Waltham, Massachusetts 02452
3 ADR1 Zoning Dept.
3 ADR2 610 Main Street
3 CITY Waltham
3 STAE Massachusetts
3 POST 02452
2 EMAI zoning@@example.com

10-WWW

This person has an OCCU event with an ADDR subrecord followed by a WWW subrecord.

GEDCOM 5.5 did not include the WWW subrecord, so target applications that read GEDCOM 5.5.1 files as if they were GEDCOM 5.5 files may reject or ignore the subrecord.

Test Result Criteria

1 OCCU Clerk
2 DATE 1900
2 ADDR City Hall
3 CONT 610 Main Street
3 CONT Waltham, Massachusetts 02452
3 ADR1 City Hall
3 ADR2 610 Main Street
3 CITY Waltham
3 STAE Massachusetts
3 POST 02452
2 WWW http://example.com