266
edits
Changes
From Gramps
→Proposals
#) Use only one mechanism for ADDR records. Do away with Place, type 'Details' and, Location Object (place Alt Location).
#* It has been suggested that Gramps developers want to deprecate the Location (Alt Location) structure of our place object. In this case the proposal is to convert stand-alone event ADDR to places with Type 'Address'. Events that also have the PLAC tag would create a place with Type 'Address' from ADDR data and then create a second (enclosing) place from PLAC data. In either case, the ADDR data would be converted to a single line of comma separated elements (if not already available).
#) Don't force fit PLAC.FORM records to Location objects, just make appropriate places with type as value from the FORM. Enclosed by hierarchy defined by GEDCOM L FORM5.5. Any place types in 1 FORM list after 'country' would not be part of hierarchy. GEDCOM L actually says to use first 4 levels, { place, county/district, state, country} but I've got a few files where leading levels are {address, street, city,…}. Postal codes are expected after 'country' level and don't participate in enclosed by hierarchy, but should be recognized if at another position. Have another file with {2 FORM Town, Area code, County, Region, Country, Subdivision} for example, which needs to work.
#: The following Example would create a Gramps place, Named '123 Main', type 'Street' with code '77375' enclosed by
#: another Gramps place, Named 'Houston', type 'City' enclosed by
