I believe that the mapping feature only uses the location field, so if you want to show a map with multiple locations within a city, putting the address in the location field would be necessary.
On Fri, Feb 11, 2011 at 2:22 PM, Paul Gray <[email protected]> wrote: > There has been lots of good discussion in the past about the pros and cons > of putting the full address (e.g. cemetery name, hospital) in the location > field vs. the address table. Until recently, I was in the 'use the address > table' camp, but I have changed my mind. > > I still think it's more correct from a database point of view to use the > separate address table, but it does cause problems when exporting/importing > a GEDCOM to other applications. Legacy creates the appropriate fields in the > GEDCOM, but in the two other applications I am familiar with (Family Tree > Maker and Roots Magic) , there is no equivalent of the address table for > locations. So, the address is simply lost. > > All applications have a location/place field. So, if you put the full > address in Legacy's location field, you are pretty much assured that you > will retain it when importing into other locations. If you use the separate > address table, the other applications may or may not import all of the > address. > > If you are not planning on exporting GEDCOMs to be used in other > applications, this probably doesn't matter. But if you are, putting the full > address in the location field increases the chances that the transfer to the > other application won't lose some data. > > Paul > > > > > > From: [email protected] [mailto:[email protected]] > Sent: February-11-11 2:34 PM > To: [email protected] > Subject: Re: [LegacyUG] cemetery entries > > I always use the burial address. When going into burial address, you > should click on Address List to see if you have already entered that > location before. If you have, you can merge duplicated addresses etc. > Within the Address List, you can click on Show List to see who else is > buried there. It's a very slick process. It seems like all of the reports > that people go through is far more time consuming with more steps than > necessary. But then we have choices for people to use Legacy in the way > that works best for that individual. > > God bless, > Ellen > > ----- Original Message ----- > From: "Connie Sheets" <[email protected]> > To: [email protected] > Sent: Friday, February 11, 2011 12:21:38 PM > Subject: Re: [LegacyUG] cemetery entries > > It appears to me you are asking at least two separate questions: > > (1) How best to enter cemetery locations? > > This is a personal choice; there is no standard way to do this nor does > there need to be. I never use the Burial Address field, but most of my > research is in rural areas. (I might feel differently if I were dealing > with more urban locations, although I doubt it). Instead, I put the name of > the cemetery in the Buried Location field, e.g. > > Cedar Hill Cem., Blythedale, Harrison Co., Missouri > > I sort my locations right to left and can easily print a list of everyone > buried in that cemetery from the Master Locations List. > > (2) How do I record that I'm using copyright information with permission? > > As Ron has suggested, I would use the Comments field of the Master Source > screen (or Source Detail, whichever is most appropriate) to record that > information. If you want it printed on your reports, be sure to check the > box on that screen that provides for that option. > > Hope this helps, > > Connie > > --- On Fri, 2/11/11, Lowell Thompson <[email protected]> wrote: > > What is the best way to enter cemetry data? I have some with the cemetery > name > in the Burial location and some with the name in the description field of > cemetery event with address in comment field and plot location also in the > comment field. I want to be able to access all entries in a cemetery. I can > find > on standard for this and several other entries ie census and some marriage > data. Is there a prefered or standard for particular data entries? > Format of Source List is not standardized. When using copywrited data with > permission how am I to be sure all manditory data is printed or gathered? > I know there are several questions in one query, but I have finally reached > a > level where I am not just gathering information but sorting and displaying > my > results. Thank you for any assistance. > L. Wayne Thompson > > > > > > > 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
