<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.6001.18975"> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV>But you do that right now when all you know is the township name, don't you?  You name the township.  Someone then has to go searching to find where that township is located. But if we had an agreement to use coordinates referencing the township (approximate central point), at least the township could be located easily by anyone with even elementary understanding of something like google maps.</DIV> <DIV> </DIV> <DIV>Addresses are either specific or general.  All I'm suggesting is to use coordinates in that same way. The key would be what is footnoted.  If just a township, then the coordinates give the approximate location. After all it would be tagged to a location name, so you really don't lose anything. The township would still be referred to by a name (except that it would be attached to a set of approximate coordinates).</DIV> <DIV> </DIV> <DIV>Once a specific location was found in that township,  footnoted coordinates would attach to that specific address within the township. </DIV> <DIV> </DIV> <DIV>But you're still "naming" the locations according to your naming preference.  Coordinates are added to the name (and if multiple jurisdictional names apply to a location, they can all be keyed to the same coordinates).</DIV> <DIV> </DIV> <DIV>I think a procedure or guidelines could be set out that would rationalize the use of coordinates in conjunction with the usual naming practices that we now use.</DIV> <DIV> </DIV> <DIV>If only we had options where we could be so specific (or generally specific) in other areas of our research.  Coordinates would bridge the gap between name and location, making mapping and finding/comparing locations (and many other options) available </DIV> <DIV> </DIV> <DIV>It's in addition to current practices, not replacing them!</DIV> <DIV> </DIV> <DIV>Larry</DIV> <DIV>----- Original Message ----- </DIV> <BLOCKQUOTE style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A title=clsheets1@yahoo.com href="mailto:clsheets1@yahoo.com">Connie Sheets</A> </DIV> <DIV style="FONT: 10pt arial"><B>To:</B> <A title=apgpubliclist@apgen.org href="mailto:apgpubliclist@apgen.org">apgpubliclist@apgen.org</A> ; <A title=apgmembersonlylist@apgen.org href="mailto:apgmembersonlylist@apgen.org">apgmembersonlylist@apgen.org</A> </DIV> <DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, October 25, 2010 7:33 PM</DIV> <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [APG Public List] place names</DIV> <DIV><BR></DIV>I must admit to only a general knowledge about, and frequent lack of attention to, GPS coordinates. I have been operating under the assumption they describe a specific point on the earth, not a large area like a rural US township of 36 square miles.<BR><BR>I can comprehend how I might want to visit the crossroads approximately one mile southeast of a very small village in Northwest Missouri where my great-great grandfather's house once stood, obtain the GPS coordinates, and record them for posterity with a photograph I have of the house. I also understand how GPS coordinates are useful for locating cemeteries, graves within cemeteries, and other landmarks.<BR><BR>However, if all I know about an ancestor's location is a rural township or county, I would be concerned that I was promoting inaccuracy if I arbitrarily chose (and yes, it would be arbitrary) the center of the township or county.<BR><BR>I will continue to use standard historical place names, with a reference to the modern place name when necessary, for the foreseeable future.<BR><BR>Connie Sheets<BR>Arizona<BR><BR><BR></BLOCKQUOTE></BODY></HTML>