I'm sorry

as of this morning, I only have 10,733 places




I have no way to separate the true "Municipalities" that are a city/town or
county or state or country or township
from all of the other locations, that are churches, or cemeteries or other
"non-municipalities'

I trust the geo-co-ordinates on all the municipalities.

I have learned not to trust any automated process that geo-coding the
others.

How can Legacy geocoding place the same  long of  451239.303  and lat
of -932434.285  for
Calvary Cemetery East, Los Angeles, Los Angeles, California, USA
Calvary Cemetery, Delavan, Minnesota, USA
Calvary Cemetery, Cloquet, Minnesota, USA







On Thu, Feb 27, 2014 at 11:45 AM, Howlanddavisii <howlanddavi...@aol.com>wrote:

> Jay:
>
>     I would hope, for CE's sake, that the first ten words of your first
> sentence was also tongue in cheek <G>.
>
> Howland Davis
>  -----Original Message-----
> From: Jay 1FamilyTree <1familytree....@gmail.com>
> To: legacyusergroup <legacyusergroup@LegacyUsers.com>
> Sent: Thu, Feb 27, 2014 1:39 pm
> Subject: Re: [LegacyUG] Entering info in location field
>
>  CE,
>
>  Let me send you my file with over 11,000 places and you tell me how much
> "modicum of effort" it takes before you realize that at some point we need
> to rely on automated processes and 'trust' that they do the job properly.
> Can you send it back to me with all the places properly fixed to the
> correct spot on the map by the end of next week?
>
>  (Please realize that last line is "tongue-in-cheek")
>
>
>
>
>
>
> On Wed, Feb 26, 2014 at 10:33 PM, CE WOOD <wood...@msn.com> wrote:
>
>>  Ah, but with a only a modicum of effort, you can easily find the
>> location and enter the coordinates into the location in Legacy. Then it
>> will appear on any map even if there is nothing there but a field, forest,
>> or some new shopping center.
>>
>> CE
>>
>> ------------------------------
>> From: 1familytree....@gmail.com
>> Date: Wed, 26 Feb 2014 21:30:12 -0800
>> Subject: Re: [LegacyUG] Entering info in location field
>> To: legacyusergroup@LegacyUsers.com
>>
>> Nope I dont because then the location wont be found on a map.
>>
>>
>> On Wed, Feb 26, 2014 at 8:36 PM, Tammyj <tam...@brightok.net> wrote:
>>
>>      Sorry folks, didn't mean to open a can of worms!  My grandmother
>> was born in 1904 before Oklahoma became a  state.  Don't y'all put the
>> location in as it was at the time in history?  I have my grandmother's
>> birth location as: Pickens Co., Chickasaw Nation, Indian Territory other
>> great-grandmother as (west of) Cumberland, Pickens Co., Chickasaw Nation,
>> Indian Territory.
>>
>>  ------------------------------
>>  *From:* Tammyj [mailto:tam...@brightok.net]
>> *Sent:* Wednesday, February 26, 2014 4:52 PM
>> *To:* legacyusergroup@LegacyUsers.com
>> *Subject:* [LegacyUG] Entering info in location field
>>
>> Entering place in the location field. I'm coming from FTM16 to Legacy 8.
>> I was wondering if there is a preferred way to enter information in the
>> location field. I would like to know how others are entering location for
>> census events as well.
>> I did it this way in FTM for the location field:
>>
>> Madill, Marshall Co., Oklahoma
>>
>> For census events I did the reverse:
>>
>> Oklahoma, Marshall Co., Wills Twp., etc....
>>
>> Is there a way it should be done to work with maps?
>>
>> I have noticed some not listing the Co.,:
>>
>> Madill, Marshall, Oklahoma
>>
>> If you put the Country do you use USA or United States?
>>
>> Thanks,
>> Tammy
>>
>>
>>
>> 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/legacyusergroup@legacyfamilytree.com/
>> 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
>>
>
>
>
> 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/legacyusergroup@legacyfamilytree.com/
> 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
>
>
> 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/legacyusergroup@legacyfamilytree.com/
> 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
>



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/legacyusergroup@legacyfamilytree.com/
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

Reply via email to