Jerry, That’s what I use for my TNG site and then when you do then you just have to go to your site and accept the custom tags you want and ignore the ones you don't. Once I have all the tags that I want I save the Gedcom file options and then when I want to create a new Gedcom upload I just load that file with the custom settings, and create the new gedcom. What I do: File>Export to GEDCOM then choose Produce file for: Legacy, Character Set: ANSI I have these boxes checked: Keep embedded formatting codes within text, Convert formatting codes to HTML style, and Override Source options - include all source information. Records Selection: All Records in the Entire Family. Then I click on the Customize... button and go through the list of available for export and move the ones I want to the Export these items under Groups of items to EXCLUDE from Export I have the following checked: Address/Phone and To-Do items if you haven't already done it then Save the List: then when you do a new one just click Load List and pick the file you saved it as, it will have a file extension of .gel When done with that screen click OK and then you can select File Name and START EXPORT.
Russ -----Original Message----- From: Jerry Sent: Thursday, November 03, 2011 8:56 PM To: [email protected] Subject: Re: [LegacyUG] export a group of people Thanks Brian. I was just wondering because when I export a GEDCOM from LEGACY and create a GEDCOM 5.5 file with it, I am not able to transfer the longitude / latitude information for the Google mapping system to our website. But when I create a GEDCOM file FOR LEGACY, as you stated, I am able to transfer the longitude / latitude information to the website just fine. My website cannot utilize a LEGACY (.fdb) file directly, but must use a GEDCOM for the transfer. So, I have learned through trial and error to use the GEDCOM that is being designed for LEGACY even though the file is transferred to a TNG (The Next Generation of Genealogy Sitebuilding) website and not to LEGACY, if that is making sense to you. Jerry Boor / http://www.MerriamFamilyTree.org On 11/03/2011 04:57 PM, Brian/Support wrote: > Jerry, > > If you export as a Legacy file you are NOT exporting a GEDCOM. You are > creating a new .fdb file that can be opened directly in Legacy. > > If you are talking about exporting a GEDCOM for Legacy versus exporting > a GEDCOM in GEDCOM 5.5 format they are both GEDCOM files however the > file designed for Legacy will include special tags to tell Legacy where > to store information that the GEDCOM 5.5 standard does not use. These > are for special data that Legacy uses. > > Brian > Customer Support > Millennia Corporation > [email protected] > http://www.LegacyFamilyTree.com > > We are changing the world of genealogy! > When replying to this message, please include all previous correspondence. > Thanks. > > On 03/11/2011 3:32 PM, Jerry wrote: >> Can someone clear something up for me? When you export and create a >> gedcom file from Legacy as a Legacy file instead of a regular gedcom 5.5, >> what are the differences? They both become gedcoms, right? Thanks, >> Jerry > 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
