GEDCOM/ADDR-Tag

From GenWiki

Jump to: navigation, search

Contents


This page is an English extract of the German page GEDCOM/ADDR-Tag [1], for full details see the German page.

Name and Meaning

Tag

ADDR

Meaning

ADDRESS

Usage

Text to describe address data in GEDCOM files. These addresses can be set up for individuals, organizations, companies etc. The addresses include both information that is required for mailing ( street, number, city, zip, country ), as well as information about telephone, fax, email and homepages.

The address structure and thus the tag ADDR may be used in the following contexts:

  • at the submitter record ( SUBM, level 1 )
  • at the repository record ( REPO, level 1 )
  • at the header of the file ( HEAD, below 2 CORP as level 3 )
  • at EVENT_DETAIL and therefore in all events and attributes in personal and family records ( each as level 2 )

Other uses are not permitted .

Formal Description of Permissible Values

Base: GEDCOM Standard Draft 5.5.1

Addresses can be represented in a GEDCOM file by the following structure:

ADDRESS_STRUCTURE:=
n ADDR <ADDRESS_LINE> {1:1}
+1 CONT <ADDRESS_LINE> {0:3}
+1 ADR1 <ADDRESS_LINE1> {0:1}
+1 ADR2 <ADDRESS_LINE2> {0:1}
+1 ADR3 <ADDRESS_LINE3> {0:1}
+1 CITY <ADDRESS_CITY> {0:1}
+1 STAE <ADDRESS_STATE> {0:1}
+1 POST <ADDRESS_POSTAL_CODE> {0:1}
+1 CTRY <ADDRESS_COUNTRY> {0:1}
n PHON <PHONE_NUMBER> {0:3}
n EMAIL <ADDRESS_EMAIL> {0:3}
n FAX <ADDRESS_FAX> {0:3}
n WWW <ADDRESS_WEB_PAGE> {0:3}

ADDR is a mandatory field in the address structure { 1:1 }, the others may be used once { 0:1 } or three times { 0:3 }. According to this specification, it is not permissible to use the tags PHON, EMAIL, FAX or WWW without the flag ADDR, although these tags are not sub-tags to ADDR.

The address is represented as a multi-line address field ( ADDR and max. 3 CONT - line, or ADDR with the lines ADR1, ADR2, ADR3 ). The standard defines:

ADDRESS_LINE:= {Size=1:60}

Typically used to define a mailing address of an individual when used subordinate to a RESIdent tag. When it is used subordinate to an event tag it is the address of the place where the event took place. The address lines usually contain the addressee’ s name and other street and city information so that it forms an address that meets mailing requirements.

Both versions ADDR + CONT and ADDR with ADRi are closely related:

ADDRESS_LINE1:= {Size=1:60}

The first line of the address used for indexing. This is the value of the line corresponding to the ADDR tag line in the address structure.

ADDRESS_LINE2:= {Size=1:60}

The second line of the address used for indexing. This is the value of the first CONT line subordinate to the ADDR tag in the address structure.

ADDRESS_LINE3:= {Size=1:60}

The third line of the address used for indexing. This is the value of the second CONT line subordinate to the ADDR tag in the address structure.

The following assignments applies:

  • 1 ADDR == 2 ADR1 (1st line of an address field)
  • 2 CONT == 2 ADR2 (2nd line of an address field, 1st CONT line)
  • 2 CONT == 2 ADR3 (3rd line of an address field, 2nd CONT line)
  • 2 CONT (4th line of an address field, only by 3rd CONT line)

With the tags CITY, POST, STAE and CTRY sub elements from the mailing address are replicated in a structure, to be written in appropriate data fields by programs with a detailed address management. The standard defines:

The ADDR and CONT lines are required for any address. The additional subordinate address tags such as STAE and CTRY are provided to be used by systems that have structured their addresses for indexing and sorting. For backward compatibility these lines are not to be used in lieu of the required ADDR and CONT line structure.

Agreements for ADDR

The agreements for ADDR are derived from the discussion on the Gedcom-L. They were decided by a vote of the program authors of the list.

A1 Export of Postal Address

With the tag ADDR and the sub-tag CONT the mailing address is exported in the form as it would be on a letter. Substantially is the input of the user into a corresponding multiple-line field or, in the absence of such address field, what the program assembled from individual sub-elements. For this alternatively assembling the same process as in A2 is recommended.

The restriction in the GEDCOM standard on max. 3 following lines with CONT is waived. According to the agreement E2 for field lengths, the structure of the data field of the program has priority: Has this data field more than 4 lines and they are filled with data, more than 3 CONT lines will be added to ADDR.

A2 Import of Postal Address

For programs with a multi-line address field for the mailing address following recommendations are made for import:

For programs with a limited number of continuation lines in the data field for the mailing address it is recommended to attach the content of further continuation lines to the last line, each separated by comma.

Has the file to be imported no CONT lines, but structured elements ADR1, ADR2, ADR3, CITY, POST, STAE or CTRY, it is recommended to include these informations in the multiline field of postal address in the following form:

1 ADDR ( ADDR )
2 CONT ( ADR1 )
2 CONT ( ADR2 ), ( ADR3 )
2 CONT ( POST ), ( CITY ), ( STAE ), ( CTRY )

This means to add the text following the parenthetical tags.

A3 Export of Structured Elements of the Postal Address

In addition to the prescribed export the mailing address according to A1 programs with an internal address data structure must also export the structure as a sub-line of ADDR. For this the standard tags ADR1, ADR2, ADR3, CITY, POST, STAE and CTRY will be used. If the mailing address also includes the name of the addressee, it is recommended to export this by means of a tag _NAME as a sub-tag of ADDR.

A4 Export of further Structured Address Elements

Besides ADDR as mandatory line other elements with tags PHON, EMAIL, FAX and WWW, specified in the GEDCOM standard, may be exported. For the contradictory information in the standard about email, it is agreed that EMAIL ( and not EMAI ) is used. Note: The general rule of the standard to use 3 or 4 characters in length, is not met.

A5 Summary of the Address Structure for Export

In compliance with the above agreements a total export of an address looks like this:

ADDRESS_STRUCTURE:=
n ADDR <ADDRESS_LINE> {1:1}
+1 CONT <ADDRESS_LINE> {0:M}
+1 _NAME <NAME_OF_ADDRESSEE> {0:1}
+1 ADR1 <ADDRESS_LINE1> {0:1}
+1 ADR2 <ADDRESS_LINE2> {0:1}
+1 ADR3 <ADDRESS_LINE3> {0:1}
+1 CITY <ADDRESS_CITY> {0:1}
+1 STAE <ADDRESS_STATE> {0:1}
+1 POST <ADDRESS_POSTAL_CODE> {0:1}
+1 CTRY <ADDRESS_COUNTRY> {0:1}
n PHON <PHONE_NUMBER> {0:3}
n EMAIL <ADDRESS_EMAIL> {0:3}
n FAX <ADDRESS_FAX> {0:3}
n WWW <ADDRESS_WEB_PAGE> {0:3}

A6 Purpose of the Address Structure

According to the GEDCOM standard, the address structure from A5 must be used exclusively in the following cases:

  • at the submitter record ( SUBM, level 1 )
  • at the repository record ( REPO, level 1 )
  • at the header of the file ( HEAD, below 2 CORP as level 3 )
  • at EVENT_DETAIL and therefore in all events and attributes in personal and family records ( each as level 2 )

A7 Addresses in Individual ( INDI ) and Family ( FAM ) Records

If during importing a file, the address structure is found in individual or family records on level 1, contrary to the requirements of the GEDCOM standard, it is recommended for a potential following re-export, to place the address structure under the tag RESI, e.g.:

0 @I1@ INDI
1 NAME Max /Mustermann/
1 RESI
2 ADDR Musterstr. 3
3 CONT 12345 Musterstadt
...

Deviation from Standard Use

There are programs that use ADDR at level 1 in individual or family records. This is a clear violation of the GEDCOM grammar.

Personal tools
GenWiki-internal
In other languages