This conversation has gotten absurd.  If you don’t want to be a genealogist, 
then don’t follow the standards that have been cited, go ahead and do it 
whatever way you want, it is your family.  Be aware that individuals that 
follow correct procedures will not be downloading your trees because we would 
just have to redo everything.  Please don’t use our trees, it would confuse you 
no end with our precise entry of place names.

Sent from my iPad

> On Aug 4, 2019, at 3:49 PM, R G Strong Genealogy <[email protected]> 
> wrote:
> 
> James,
> 
> Again, if you choose not to use the Genealogical Standard for places that is 
> your choice but as was said, don't publish it for those that do. It is not 
> policing it is the standard set by the Genealogists!
> 
> Russ
> 
> P.S this is starting to get old!!
> 
>> On 8/3/2019 3:14 PM, James G. Hermsen via LegacyUserGroup wrote:
>> I never had a Gedcom file not accept any location file whether it had 
>> Indianapolis, Marion Co., IN, or         even Indianapolis, IN. not to 
>> mention Indianapolis, xxx Township, Marion County, Indiana, United States of 
>> America.  You soon get the point that the latter is the creation of someone 
>> who thinks that they need to police something totally not needed by anyone 
>> with common sense, or a tad bit of education.
>> 
>> Hoosierly yours,
>> 
>> James G. Hermsen
>> 8108 Laura Lynne Lane
>> Indianapolis, IN 46217
>> 
>> 317-679-1466 cell
>> 317-881-4600 land line
>> 
>> 
>> On ‎Saturday‎, ‎August‎ ‎03‎, ‎2019‎ ‎09‎:‎43‎:‎25‎ ‎AM‎ ‎EDT, 
>> <[email protected]> wrote:
>> 
>> 
>> Christopher
>> 
>> I agree with you.
>> 
>> My suggestion of putting the present name between curly brackets after the 
>> referenced location name is simply an easy way to translate old location 
>> name into present day name and it is accepted by the different Gedcom 
>> programs.
>> 
>>  
>> 
>> Georges
>> 
>>  
>> 
>>  
>> 
>> De : LegacyUserGroup <[email protected]> De la part de 
>> Christopher Seward Sr
>> Envoyé : 3 août 2019 09:21
>> À : Legacy User Group <[email protected]>
>> Objet : Re: [LegacyUG] Location names for Pennsylvania
>> 
>>  
>> 
>> James, I understand where you're coming from. I just think that handling 
>> data in a manner that deviates from the standard is inviting data integrity 
>> issues. As I said,  the choice is yours. Just be aware of the lasting issues 
>> it will cause for those who come after.
>> 
>>  
>> 
>> Christopher 
>> 
>>  
>> 
>> On Sat, Aug 3, 2019, 4:59 AM James G. Hermsen via LegacyUserGroup 
>> <[email protected]> wrote:
>> 
>> Exactly my point.  Putting historical location in the notes maintains all 
>> the information one needs and still be sensible and useful to family 
>> members.  If people import information without looking at the notes, then 
>> they are not being a good genealogist.   It tells me that they just copy 
>> things for numbers, not for reliable and useful information to share.
>> 
>>  
>> 
>> Hoosierly yours,
>> 
>>  
>> 
>> James G. Hermsen
>> 
>> 8108 Laura Lynne Lane
>> 
>> Indianapolis, IN 46217
>> 
>>  
>> 
>> 317-679-1466 cell
>> 
>> 317-881-4600 land line
>> 
>>  
>> 
>>  
>> 
>> On ‎Friday‎, ‎August‎ ‎02‎, ‎2019‎ ‎08‎:‎51‎:‎50‎ ‎AM‎ ‎EDT, Bill Hoff 
>> <[email protected]> wrote:
>> 
>>  
>> 
>>  
>> 
>> Then one cannot find on a map if historic locations used. With many 
>> relatives in West Virginia I have this problem. WV did not become a state 
>> until June 20, 1863.  On top of that many counties within the state were 
>> divided over many years, far too many for me to recall them all. Then there 
>> is the problem of knowing locations but not dates so one cannot be certain 
>> of entries 
>> 
>> Bill
>> 
>> Sent from my iPhone
>> 
>> 
>> On Aug 1, 2019, at 8:15 PM, Christopher Seward Sr. <[email protected]> 
>> wrote:
>> 
>> You are free to record as you choose, but keep in mind that if you publish & 
>> share this information, your method goes against the standard, and can cause 
>> issues. 
>> 
>> An example for me was importing a person's info into my file.  I kept 
>> getting import errors stating the the location (birth place) did not exist 
>> on that date (birth date).  Now I have an issue, since this place not only 
>> didn't exist when this person was born, but when it did exist, it was in a 
>> different country than when he was born, thus making him appear to be of one 
>> heritage, but was actually another.
>> 
>> I recommend ALWAYS putting the correct location in, and putting the current 
>> name of the location in the notes.
>> 
>> On 8/1/2019 4:41 PM, James G. Hermsen via LegacyUserGroup wrote:
>> 
>> Yes, but in the notes.  Most people I share my information with want to know 
>> where the place is now.  They, like Trump, have no regard for history, and 
>> those who know their history, already know what the original name is.  
>> Looking for documents, the current place will know what jurisdiction they 
>> once were  governed by.  It is all about being usable for current people.  
>> Otherwise, we would all be recording everying in Latin like they once did.
>> 
>>  
>> 
>> Hoosierly yours,
>> 
>>  
>> 
>> James G. Hermsen
>> 
>> 8108 Laura Lynne Lane
>> 
>> Indianapolis, IN 46217
>> 
>>  
>> 
>> 317-679-1466 cell
>> 
>> 317-881-4600 land line
>> 
>>  
>> 
>>  
>> 
>> On ‎Thursday‎, ‎August‎ ‎01‎, ‎2019‎ ‎01‎:‎22‎:‎29‎ ‎PM‎ ‎EDT, 
>> [email protected] <[email protected]> wrote:
>> 
>>  
>> 
>>  
>> 
>> I think one should always the name of a location the way it is indicated in 
>> the documentation.
>> 
>> If the name has change or if two locations have been merge, I use curly 
>> brackets with the new name after the old name.
>> 
>> Ex.  Romorantin {Romorantin-Lanthenay}, 41194, Loir-et-Cher, Centre-Val de 
>> Loire, France
>> 
>> (Note : I use 5 fields)
>> 
>>  
>> 
>> Georges
>> 
>>  
>> 
>> De : LegacyUserGroup <[email protected]> De la part de 
>> James G. Hermsen via LegacyUserGroup
>> Envoyé : 1 août 2019 09:26
>> À : mvmcgrs--- via LegacyUserGroup <[email protected]>
>> Cc : James G. Hermsen <[email protected]>
>> Objet : Re: [LegacyUG] Location names for Pennsylvania
>> 
>>  
>> 
>> I always use the current geographic location and name today in each entry 
>> and in the notes, remark that the geographic name and country was different 
>> then than it is today.  That way when a grandchild (or anyone) wants to find 
>> the place on a map is able to do so.  Prussia is very hard to find, if you 
>> did not know where to look. Same thing with names of cities whose name has 
>> changed.  Stalingrad, Linengrad don't make sense for someone born after the 
>> Cold War.   Peking vs. Bejing.  Same thing.
>> 
>>  
>> 
>> Hoosierly yours,
>> 
>>  
>> 
>> James G. Hermsen
>> 
>> 8108 Laura Lynne Lane
>> 
>> Indianapolis, IN 46217
>> 
>>  
>> 
>> 317-679-1466 cell
>> 
>> 317-881-4600 land line
>> 
>>  
>> 
>>  
>> 
>> On ‎Thursday‎, ‎August‎ ‎01‎, ‎2019‎ ‎08‎:‎43‎:‎54‎ ‎AM‎ ‎EDT, mvmcgrs--- 
>> via LegacyUserGroup <[email protected]> wrote:
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> I hope you are not inserting the the added information if it is not in the 
>> document.  The jurisdictions change over time. In the US what was a county 
>> in 1850 may be another county in 1860 and still another county by 1870. The 
>> house did not move but the boundaries did.
>> 
>>  
>> 
>> Marie
>> 
>> Marie Varrelman Melchiori, Certified Genealogist Emeritus
>> ______________________________ ______________________________ __
>> CG or Certified Genealogist is a service mark of the Board for Certification 
>> of Genealogists, used under license by Board-certified genealogists after 
>> periodic competency evaluation, and the board name is registered in the US 
>> Patent & Trademark Office.
>> 
>> In a message dated 8/1/2019 6:24:51 AM Eastern Standard Time, 
>> [email protected] writes:
>> 
>>  
>> 
>> I do agree.  
>> 
>>  
>> 
>> My standard is:   [1. local jurisdiction/repository i.e.township, village, 
>> city, etc], 2.County, 3.State, 4.Country 
>> 
>> and apply to other countries similarly by always using three commas for all 
>> locations [usually each has a repository of genealogical data] .  The entry 
>> might between comma's might be null if I don't have the information.  For 
>> example born in USA might be ", , , USA".  I know I have some research to do 
>> but I only record what I have from that source.
>> 
>>  
>> 
>> For folder hierarchy and some naming situations I reverse the order but 
>> always hold to 4 elements for location.  I don't believe I have ever had an 
>> exception.  I am sure I will learn about one here.  So far this works for 
>> me. 
>> 
>>  
>> 
>> Bill
>> 
>>  
>> 
>> On Wed, Jul 31, 2019 at 12:20 AM Roberta Schwalm <[email protected]> 
>> wrote:
>> 
>> I do the same thing, Shirley.  Most of my ancestors are from Scotland, 
>> Ireland, England, Germany and a spattering of French.  The only difference 
>> is I use "province" instead of State.
>> 
>>  
>> 
>> On Tue, Jul 30, 2019 at 9:05 PM Shirley Crampton <[email protected]> 
>> wrote:
>> 
>> I use Village, County, State, Country.  Hopefully there is no more than 1 
>> village of the same name in the County.  If the place is rural then I put 
>> the name of the township in the first position.
>> 
>>  
>> 
>> On Tue, Jul 30, 2019 at 5:47 PM Connie Laubach <[email protected]> 
>> wrote:
>> 
>> Trying to decide how to input the location names – I have townships that are 
>> made up of villages and boroughs. How are others handling it?
>> 
>> I have thought of the following:
>> 
>> Village, township, county, state, United States
>> 
>> or
>> 
>> township-village, country, state, United States (I like this as  all 
>> villages within the township would be listed together)
>> 
>>  
>> 
>> Thank you, Connie.
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> -- 
>> 
>> LegacyUserGroup mailing list
>> [email protected]
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/[email protected]/
>> 
>> -- 
>> 
>> LegacyUserGroup mailing list
>> [email protected]
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/[email protected]/
>> 
>>  
>> 
>>  
>> 
>> 
>> 
>> Virus-free. www.avast.com
>> 
>> -- 
>> 
>> LegacyUserGroup mailing list
>> [email protected]
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/[email protected]/
>> 
>> -- 
>> 
>> LegacyUserGroup mailing list
>> [email protected]
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/[email protected]/
>> 
>> -- 
>> 
>> LegacyUserGroup mailing list
>> [email protected]
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/[email protected]/
>> 
>> -- 
>> 
>> LegacyUserGroup mailing list
>> [email protected]
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/[email protected]/
>> 
>> 
> -- 
> 
> LegacyUserGroup mailing list
> [email protected]
> To manage your subscription and unsubscribe 
> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/[email protected]/
-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

Reply via email to