Mark, I doubt if the use of a colon will make any different to the mapping function, and the rest of the location certainly doesn't - it is basically the format I always use, and I do use the mapping facility. In fact from the point of view of mapping, using the full address for the location gives a much more accurate result (providing the road still exists!).
Ron Ferguson http://www.fergys.co.uk/ -------------------------------------------------- From: "Mark Klan" <m...@markabout.com> Sent: Wednesday, September 29, 2010 10:16 AM To: <LegacyUserGroup@LegacyUsers.com> Subject: Re: [LegacyUG] PLACE NAMES > I'm one of the folks who use the Buried/Location field for cemetery names > & locations, and initially this did indeed cause my master locations list > to be quite a mess. However, I got rid of the jumble by entering every > cemetery as follows (example): > > Cem: Trinity Cemetery, Sylvania, DeKalb, Alabama, United States > > Then for the short version, I edit and remove "Cem: " and also ", United > States". I do this in the Master Locations list after I have added some > new cemeteries, or whenever I get around to it. Once it's done for any > given cemetery, it's done. > > So this particular cemetery shows up naturally on screen and in reports as > Trinity Cemetery, Sylvania, DeKalb, Alabama. And in the master location > list, all of my cemeteries are grouped together alphabetically beginning > with the prefix Cem:<space>. This eliminated the mess. I imagine it > won't work well if you are using the mapping/lat/long stuff, but I > don't... :-) > > Maybe this approach will be helpful to someone out there. > > Mark > > **** > Wednesday, September 29, 2010, 12:09:22 AM, Jerry wrote: > > For what it's worth, my opinion is to use the BURIED field only as a > location field such as Detroit, Wayne Co, Michigan, USA - then add the > name of the cemetery in the NOTES field next to the BURIED location field. > Otherwise, you will get LOCATION names that refer to CEMETERIES and not > CITIES, VILLAGES, TOWNSHIPS, etc. The LOCATION fields are much more > manageable not to mix them up with CEMETERY names.....IMO. Plus, if you > ever use TNG - The Next Generation of Genealogy Sitebuilding for your > website data, you will have very messy PLACE names if you use CEMETERIES > in fields that are really designed only for the traditional LOCATION / > PLACE divisions. > > Jerry > > On 9/28/2010 10:41 PM, Jacki Richey wrote: > > Tim, why do you create a 'burial' event when Legacy has a place for > "buried" right after "died"? > >> From: spa...@xmission.com >> Jenny, > >> Would one enter the Cemetery like this ? > >> Forrest Lawn Cemetery, L. Street, Plot 5.4, Cypress, Orange, California, >> USA > >> I'm like Sherry. I create a 'Burial' event. > >> Tim > >> > On 27/09/2010 19:13, Sherry/Support wrote: >> >> I enter the cemetery name as an Event. That's easy to search and >> >> create reports on. Some users enter the cemetery name and address info >> >> using the Address feature for the Burial field. Click on the "+" at >> >> the end of the field to enter the event address. >> > >> > And some of us enter the cemetery name as part of the location. Indeed, >> > I include not only the cemetery name but also the plot/grave number >> > when >> > I know it. >> > >> > What's best is what works for you! Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
