Matt, thank you for your comprehensive reply. I don't know the latitude and longitude of any of my locations at present. I live in Australia, and don't' know if the resources you mention are available here. I will check. I am not too concerned about the exact address of any of my cemeteries, hospitals or churches as I figure people can look them up themselves.
For the time being, I think I will use your way of incorporating the cemetery name in the location address, because I just really don't like the present only available option of putting the cemetery name and address below the location in reports. I may even do that for other principal events. I think we will just have to agree to disagree about the desirability of a Local Site field. It is not for the recording of the information I want it - as you point out Legacy covers that. It is the way reports read that concerns me. Jennifer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Henderson Sent: Monday, 26 September 2005 11:53 AM To: [email protected] Subject: RE: FW: [LegacyUG] Local site field Jennifer, Jim is correct in that the four principle events do not support a description field. If you have an Alternate Death with the "Local site field" in the description and you want to swap the Alt Death with the main Death, whatever is in the description will now be a part of the Swapped Death information. That is why I stick to the Address field for Hospitals, AFB, Churches, and other buildings. Cemeteries are the only thing I incorporate in the Location list, but I do not use a comma. It is part of the City or County, ie, Austin in Assumtion Cemetery, Travis County, Texas, USA The GeoDatabase does not like this, though, so I never try to use it with Cemetery locations. I am currently putting all Cemeteries in my Event Addresses. Physical addresses for even rural cemeteries is easy using Google Maps http://maps.google.com/ Just type in the decimal format of the latitude and longitude of the cemetery like 34.1903, -118.36 in the Google map search field and it will produce a map with streets and or county roads, with a map, satellite or hybrid view option. I then select the "LINK to This Page" then copy the webste address and paste it into the Homepage part of the address field. If Findagrave.com has a map of the cemetery I opaste that webaddress in the Homepage button. I then have a map address that will print on reports when I have the Event Address Option selected in Reports. Anyone seeing my reports can then see exactly where the Cemetery is (or Church, Hospital, etc, - Street address, city, State typed into Google maps produces a map also). This can be a time consuming task if you have a lot of addresses. But genealogy is a time consuming hobby, yes? Having the Findagrave.com web address for the cemetery is also good thing, because I can Show list for the Cemetery Address and print a list for every one using that Cemetery so that I can later submit their burials to the findagrave.com listing if they are not shown in that findagrave listing. The Address Field is the best current method Legacy has as an alternative to the local site field. It works for me. I see no need for Legacy to create a local site field, that would be redundant because a local site field is nothing more than an address. Cemeteries are an exception, because they often do not have mailing addresses like Churches and Hospitals. After all, who is going to read the mail at a cemetery! Matt Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
