GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 

GenoPro Support Forum


Home » GenoPro » Bug Report » Errors with Gedcom import


Errors with Gedcom import

Click to view RSS...
Author BAPM tag not recognised
appleshaw
Posted Thursday, November 8, 2012 - Post #30878
Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master

Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 43 minutes ago
Posts: 1,576, Visits: 31,221
I have been testing Gedcom features and find the the BAPM tag is converted into a Custom Tag on import.
I created an individual and exported through both Gedcom versions. The Report version gives
0 @ind00001@ INDI
1 NAME John /Doe/
2 GIVN John
2 SURN Doe
1 SEX M
1 BIRT
2 DATE 14 JAN 1933
1 BAPM
2 DATE 15 FEB 1934
But on import creates a Custom tag. The other version does import but this is not standard
0 @ind00001@ INDI
1 NAME John /Doe/
2 DISPLAY John Doe
2 GIVN John
2 SURN Doe
1 POSITION -90,300
2 BOUNDARYRECT -124,332,-56,253
1 SEX M
1 BIRT
2 CEREMONYTYPE Baptism
2 DATE 14 Jan 1933
2 BAPTISM
3 DATE 15 Feb 1934
appleshaw
Posted Sunday, November 25, 2012 - Post #30942
Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master

Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 43 minutes ago
Posts: 1,576, Visits: 31,221
Although the BAPM tag in a gedcom is ignored by GenoPro, the CHR tag is recognised and imported correctly. So if the gedcom has BAPM tags they can be modified in a text editor by searching for
1 BAPM
and replacing with
1 CHR
On import the date is in the correct place but the preceding box (Baptism or Christening) is empty.

Hopefully no other problems will occur by doing this. Will report if anything else turns up.

Having worked on this I have now found that I could have saved myself a lot of trouble by using  the XML toolkit, which has options to make gedcom files GenoPro compatible. Import a gedcom, which will generate custom tage where GenoPro does not understand the tags. The toolkit then rescues them. The toolkit can be difficult to dig out of this forum. It is at
http://support.genopro.com/Topic16307.aspx

Edited: Monday, November 26, 2012 by appleshaw
appleshaw
Posted Thursday, December 20, 2012 - Post #31017
Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master

Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 43 minutes ago
Posts: 1,576, Visits: 31,221
The gedcom import creates Custom tags where there is no direct link to GenoPro fields but does not deal correctly with the SOUR tag. Where this is attached to a birth record it is imported without problem. Other ones are ignored completely. In the attached simple gedcom the birth record is correct but those under OCCU and RESI are ignored. PAF will import this file and recognize all sources

0 HEAD
1 SOUR GenoPro®
2 VERS 2.5.4.1/2012.12.19
2 CORP GenoPro Inc.
3 ADDR http://www.genopro.com
1 DATE 20 DEC 2012
1 SUBM @subm1@
1 GEDC
2 VERS 5.5
2 FORM LINEAGE_LINKED
1 CHAR UTF-8
0 @ind1941298864@ INDI
1 NAME John Thomas /Steer/
2 GIVN John Thomas
2 SURN Steer
1 SEX M
1 BIRT
2 DATE ABT 1860
2 PLAC Lower Norwood,Surrey
2 SOUR @source00109@
1 DEAT Y
1 OCCU Plasterer
2 SOUR @source00110@
1 RESI
2 PLAC 17 Church Path,Croydon,Surrey
2 SOUR @source00109@
0 @source00109@ SOUR
1 TITL 1911 census
0 @source00110@ SOUR
1 TITL RG14
0 @subm1@ SUBM
1 NAME GenoPro User
1 ADDR Not
2 CONT Disclosed
0 TRLR


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse


Powered By InstantForum.NET 2010-3-x © 2024
Execution: 0.016. 5 queries. Compression Disabled.