TNG says they reguire GEDCOM 5.5. Gene =============
At 07:55 PM 1/20/2011, you wrote: >Why not just select export as Legacy, use defaults and don't change >back to gedcom? I think that might negate your changes?? > >Gene Wheeler <[email protected]> wrote: > > >Ron, > > > >I'm using the very same setup and file. GEDCOM 5.5 does not, by > >default, include _PLAC _DEFN. You have to use the export to Legacy > >type file to get that element. so I started the process by selecting > >Legacy GEDCOM, then moved _PLAC _DEFN to the right column, then saved > >the customized definition. Then went back and redid the process, > >selecting GEDCOM 5.5, then loading the customized definition which > >brought _PLAC _DEFN back, then created the GEDCOM. After searching > >the resulting GEDCOM, there was no _PLAC _DEFN, nor LATI or LONG in > >the results! > > > >Gene > >============== > > > >At 07:03 PM 1/20/2011, you wrote: > >>Gene, > >> > >>I have been keeping an eye on this thread all day but have been a bit too > >>busy to check it out. I am running Legacy 7.5.0.40 on win7 64 bit PC and I > >>have just exported to GED 5.5 using the defaults and the LATI and LONG are > >>present in the _PLAC_DEFN records towards the end of the GEDCOM file. > >> > >>BTW. Mine are preceded with the #3 and not #4. > >> > >>Ron Ferguson > >>http://www.fergys.co.uk/ > >> > >>-----Original Message----- > >>From: Gene Wheeler > >>Sent: Thursday, January 20, 2011 11:41 PM > >>To: [email protected] > >>Subject: Re: [LegacyUG] Cannot export Lat/Long > >> > >>Jerry, > >> > >>No joy yet. I'm importing into TNG; however, that is a moot > >>point. When I inspect the GEDCOM created by Legacy, I'm not finding > >>the LATI or the LONG statement, even though virtually every location > >>in my database has been Geo-coded, even the Event locations. > >> > >>Gene > >>================= > >> > >>At 06:31 PM 1/20/2011, you wrote: > >> >Hi Gene. Did you resolve your issue? Lost in all the discussion, at > >> >least for me, is what program you are transferring your Legacy gedcom > >> >into? Just wondering if that might make any difference. I simply used > >> >the defaults, but saved my export as a Legacy file, not a gedcom, > >> >imported into TNG on my website and it worked fine. --Jerry > >> > > >> >On 01/20/2011 03:40 PM, Paul Gray wrote: > >> > > I'm at 7.4.0.45. > >> > > > >> > > I cannot export LATI or LONG for locations, using Gedcom 5.5. In > >> > fact, in customize, it's not even in the list of items available for > >> > export. > >> > > > >> > > However, in the 'export these items', the tag _PLAC_DEFN is > >> > there. However, although I have a record with lat/long, I do not > >> > get a _PLAC_DEFN record (nor as I said, get a LATI or LONG record). > >> > > > >> > > > >> > > Curious however, if I create an event address and put the > >> > co-ordinates in that table, I do get a LATI and LONG in the exported > >> > GEDCOM. > >> > > > >> > > Paul > >> > > > >> > > > >> > > > >> > > > >> > > -----Original Message----- > >> > > From: James Cook [mailto:[email protected]] > >> > > Sent: January-20-11 1:09 PM > >> > > To: [email protected] > >> > > Subject: Re: [LegacyUG] Cannot export Lat/Long > >> > > > >> > > I've exported LATI and LONG in 7.4 before. (I've not upgraded to 7.5 > >> > > yet) To clarify, are you saying the LATI and LONG options do not > >> > > appear in the "customize" options, or that the actual GEDCOM you've > >> > > exported does not contain those tags? If it's just that they do not > >> > > appear in the customize options (I don't remember if I've ever looked > >> > > for these tags specifically), try adding a tag that might include > >> > > them, or may sure you don't have one or more of the EXCLUDE options > >> > > checked that would suppress them. > >> > > > >> > > I'm not in front of my data right now, but IIRC, Legacy does not > >> > > support the 5.5.1 GEDCOM specs (which has a PLAC structure), only 5.5 > >> > > (which does not). As such, Legacy produces their own custom tag, > >> > > _PLAC_DEFN, and the LATI and LONG get nested inside of that structure. > >> > > So turning on places (or not excluding them) may help. > >> > > > >> > > > >> > > > >> > > 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 > >> > > > >> > > 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 > >> > > > >> > > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > > > >> > > > >> > > > >> > > > >> > > >> >-- > >> >Regards, > >> >Jerry in Michigan > >> > > >> > > >> > >> > >> > >> > >>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 > >> > >>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 > > > >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 > >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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
