266
edits
Changes
From Gramps
→Details
<nowiki>n PLAC <PLACE_NAME> {1:1}
+1 FORM <PLACE_HIERARCHY> {0:1}
+1 FONE <PLACE_PHONETIC_VARIATION> {0:M} New Place Alt Name(1,2) Note+2 TYPE <PHONETIC_TYPE> {1:1} New Place Alt Name Language(1,2) Note+1 ROMN <PLACE_ROMANIZED_VARIATION> {0:M} New Place Alt Name(1,2) Note+2 TYPE <ROMANIZED_TYPE> {1:1} New Place Alt Name Language(1,2) Note
+1 MAP {0:1}
+2 LATI <PLACE_LATITUDE> {1:1}
+1 <<NOTE_STRUCTURE>> {0:M}
+1 _LOC @<XREF:_LOC>@ New cross ref to _LOC
+1 _GOV <GOV_IDENTIFIER> {0:1} New (1, 2) Note
+1 _POST <POSTAL_CODE> {0:M} New (2)Place Code field
+2 DATE <DATE_VALUE> {0:1} New (1,2) Note
1) Since Gramps Places don't have Attributes, I propose that these items be placed in a single Gramps note (one per place (or place reference in the Event)). The note will have the various GEDCOM fields and the contents included.
2) If the _LOC is present, these are also expected in the _LOC structure. Between both structures and in some cases multiple copies, and a duplicate avoidance strategy is used. If the sub-record is the same as one already present in the note, it is dropped. If different, it will be ignored hereadded.
The cross referenced _LOC record is defined below and is entirely new. While these are expected at the end of the GEDCOM file per the EL agreement, Gramps can support them at any position.
1 NAME <PLACE_NAME> {1:M} Place Name
2 DATE <DATE_VALUE> {0:1} Place PlaceName Date
2 _NAMC <PLACE_NAME_ADDITION> {0:1} Place Name Note (31)
2 ABBR <ABBREVIATION_OF_NAME> {0:M} Note (1)
3 TYPE <TYPE_OF_ABBREVIATION> {0:1} Note (1)
2 <<SOURCE_CITATION>> {0:M} Citation (4)
1 TYPE <TYPE_OF_LOCATION> {0:M} Place Type (2)
2 DATE <DATE_VALUE> {0:1} Place PlaceName Date Note (21, 3)
2 <<SOURCE_CITATION>> {0:M} Citation (4)
1 _FPOST <FOKO_POSTCODE> {0:M} Note (1)
1 <<CHANGE_DATE>> {0:1}</nowiki>
1) Since Gramps Places don't have Attributes, I propose that these items be placed in a single Gramps note (one per place). The note will have the various GEDCOM fields and the contents included. When there are multiple possible similar notes (place name notes, enclosed by notes) the associated place Name or enclosed Gramps_ID (as a styledtext StyledText xref) will be included in the local heading.
2)Gramps does not support multiple place types. If more than one type is found, the TYPE and TYPE.DATE will be put in the Note.
3) Place Name AdditionType Date. Prepend to place name Gramps does not support a date on importthe PlaceType, it is put into the Note.
4) The citation will be directly on the Place, however, the note will have a heading and citation xref.
5) The event will be created as normal, and the note will have a styledtext StyledText xref to it. This is somewhat dangerous in that these events will appear to be 'unused objects' in a 'Check and Repair' or 'Unused Object' scan, and might be deleted. Also if filters are used, these events might not be included in desired output.
6) If more than one Postal code is encountered only the first is stored in the Gramps place code field. Additional encounters are stored in Note.
