Select gedcom then change "produce file for"

On Fri, Mar 30, 2012 at 3:26 PM, Cathy-0 <[email protected]> wrote:

> Jerry,
>
> where do you see "Legacy gedcom"?  When I click on the Export, I see on my
> computer only the following three options:
> -- Gedcom
> -- Legacy
> -- Clooz
>
> Of the above three, the Legacy option does not show any gedcom but a file
> extension of .fdb.
> I'm using Legacy v.7.5.0.166
>
> so, please provide some clarification.
>
> thanks,
> Cathy
>
> ----- Original Message -----
> From: "Jerry" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, March 29, 2012 12:13 AM
> Subject: Re: [LegacyUG] Latitude and longitute not being exported in GEDCOM
>
>
> > Hi Jennifer.  Did you happen to see my reply before Sherry sent her
> > reply?  I know for a fact (unless this has been changed with a later
> > version of Legacy), that you have to create an export gedcom as a Legacy
> > gedcom - you cannot create a gedcom 5.5 and transfer into TNG if you
> > want the mapping coordinates to transfer.   I'm not sure if this
> > behavior is on the Legacy end or the TNG end in the way that is handled
> > because I did not check it out what was in the gedcoms specifically.
> > I just know that when I created a regular gedcom 5.5 and transferred to
> > my TNG website, the latitude and longitude coordinates did NOT
> > transfer.   When I changed it to a Legacy gedcom, it worked just fine.
> > I'm not sure if this is your problem, but I wasn't sure if you saw my
> > post.   Cheers,   --Jerry - http://www.MerriamFamilyTree.org
> >
> > On 03/28/2012 05:48 PM, Jennifer Crockett wrote:
> >> OK - I have discovered that if I don't load the list I had prepared ages
> >> ago, everything is fine. I have used this list forever and it never
> >> created a problem before. Below is the list. Any problems there?
> >>
> >> Jennifer
> >>
> >> 0
> >> 0
> >> 1
> >> 0
> >> 0
> >> 0
> >> 0
> >> 0
> >> 1
> >> 1
> >> 1
> >> 0
> >> 1
> >> " "
> >> "*BIRT Birth"
> >> "*DEAT Death"
> >> "*MARR Marriage"
> >> "*NAME Name"
> >> "*SEX Gender"
> >> "_EVENT_DEFN Event Definition"
> >> "_GROUP Label Groups"
> >> "_NONE Had No Children"
> >> "_ORDER Order"
> >> "_PATH File Path"
> >> "_PHOTO Photo"
> >> "_PLAC_DEFN Place Definition"
> >> "_PREF Preferred"
> >> "_SOUND Sound Filename"
> >> "_STAT Status"
> >> "_TODO To-Do Items"
> >> "_UID Unique Identifier"
> >> "_VERI Verified"
> >> "_VIDEO Video"
> >> "ABBR Abbreviation"
> >> "ADDR Address"
> >> "ADOP Adoption"
> >> "AFN Ancestral File Number"
> >> "ALIA Alias Name"
> >> "ANCI Ancestor Interest"
> >> "ANUL Annulment"
> >> "ARVL Arrival"
> >> "AUTH Author"
> >> "BAPL LDS Baptism"
> >> "BAPM Baptism"
> >> "BARM Bar Mitzvah"
> >> "BASM Bas Mitzvah"
> >> "BLES Blessing"
> >> "BURI Burial"
> >> "BUYR Buyer"
> >> "CALN Call Number"
> >> "CAST Caste"
> >> "CAUS Cause"
> >> "CEME Cemetery"
> >> "CENS Census"
> >> "CHAN Changed"
> >> "CHIL Child"
> >> "CHR Christened"
> >> "CONF Confirmation"
> >> "COPR Copyright"
> >> "DATA Data"
> >> "DATE Date"
> >> "DESI Descendant Interest"
> >> "DIV Divorce"
> >> "DPRT Departure"
> >> "EDTR Editor"
> >> "EDUC Education"
> >> "EMIG Emigration"
> >> "ENDL LDS Endowment"
> >> "ENGA Engagement"
> >> "EVEN Event"
> >> "FCOM First Communion"
> >> "FIDE Fidelity"
> >> "FILM Film"
> >> "FOST Foster Child"
> >> "GIVN Given names"
> >> "GRAD Graduation"
> >> "HEAL Health/Medical"
> >> "HEIR Heir"
> >> "HUSB Husband"
> >> "IMMI Immigration"
> >> "INTV Interviewer"
> >> "ITEM Item"
> >> "LANG Language"
> >> "LGTE Legatee"
> >> "MBR Member"
> >> "MEDI Media"
> >> "MNOTE Medical Notes"
> >> "NAMS Name Sake"
> >> "NATU Naturalisation"
> >> "NOTE Notes"
> >> "NPFX Title Prefix"
> >> "NSFX Title Suffix"
> >> "OBJE Object"
> >> "OCCU Occupation"
> >> "ORDN Ordination"
> >> "OWNR Owner"
> >> "PAGE Source Detail"
> >> "PERI Period"
> >> "PHON Phone Number"
> >> "PLAC Place"
> >> "PROB Probate"
> >> "PROP Property"
> >> "PUBL Publication"
> >> "PUBR Publisher"
> >> "PURC Purchase"
> >> "RECO Recorder"
> >> "REFN User ID"
> >> "RELI Religion"
> >> "REPO Repository"
> >> "RESI Residence"
> >> "RETI Retirement"
> >> "RFN Record Number"
> >> "RNOTE Research Notes"
> >> "ROLE Role"
> >> "SELR Seller"
> >> "SERS Series"
> >> "SLGC LDS Sealed to Parents"
> >> "SLGS LDS Sealed to Spouse"
> >> "SOUR Source"
> >> "SSN Soc Sec Num"
> >> "STIL Stillborn"
> >> "SURN Surname"
> >> "TEMP LDS Temple"
> >> "TEXT Text"
> >> "TIME Time"
> >> "TITL Title"
> >> "TXPY Taxpayer"
> >> "WIFE Wife"
> >> "WILL Will"
> >> "WITN Witness"
> >> "XLTR Translator"
> >>
> >> Regards,
> >>
> >> Jennifer
> >> http://colston-wenck.com
> >>
> >>
> >> -----Original Message-----
> >> From: Sherry/Support [mailto:[email protected]]
> >> Sent: Thursday, 29 March 2012 1:48 AM
> >> To: [email protected]
> >> Subject: Re: [LegacyUG] Latitude and longitute not being exported in
> >> GEDCOM
> >>
> >> As I wrote to you in the support ticket you sent in, it is being
> >> exported in the latest build.
> >>
> >> 0 _PLAC_DEFN
> >> 1 PLAC Long Beach, Los Angeles, California, United States
> >> 2 ABBR Long Beach, Los Angeles, CA
> >> 2 _PREP in
> >> 2 MAP
> >> 3 LATI N33.7669444444444
> >> 3 LONG W118.188333333333
> >>
> >>
> >> It's possible that the importing program isn't recognizing the
> _PLAC_DEFN
> >> tag.
> >>
> >>
> >> Sincerely,
> >> Sherry
> >> Technical Support
> >> Legacy Family Tree
> >>
> >>
> >>
> >> On Wed, Mar 28, 2012 at 6:02 AM, Jennifer Crockett
> >> <[email protected]>  wrote:
> >>> Using Legacy V 7.5.0.166
> >>> Exporting GEDCOM for Legacy
> >>> It appears that Latitude and longitude are not being exported. Can
> >>> anyone
> >>> confirm this?
> >>>
> >>> If so, I now wish I had not updated to the latest version.
> >>>
> >>> Regards,
> >>>
> >>> Jennifer
> >>> http://colston-wenck.com
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> > Legacy User Group guidelines:
> > http://www.LegacyFamilyTree.com/Etiquette.asp
> > Archived messages after Nov. 21 2009:
> > http://www.mail-archive.com/[email protected]/
> > Archived messages from old mail server - before Nov. 21 2009:
> > http://www.mail-archive.com/[email protected]/
> > Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and
> > on our blog (http://news.LegacyFamilyTree.com).
> > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
> >
> >
> >
>
>
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and
> on our blog (http://news.LegacyFamilyTree.com).
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>
>



Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Reply via email to