It's probably just me. At this point, I don't know if I'll ever want or need the townsnip names.
I've got a large group of Ontario locations that use the name; such as "Ferris"and sometimes "Ferris township" for the first field. I'm never sure if the record coming in from ancestry just was inconsistent, or if there is a town and a township and I shouldn't change it. I'll need to go back to the individuals and find out if its a town or township because for consistency I would always like to record "township" after the place unless it's a city. (Also I like to keep all the info I find about the place, in case I want it somewhere down the line.) Maybe the geo locator will be more helpful later. A few times it fills in blanks and gives me counties I didn't have. But then I'm thinking those counties might not be the county that was used when the record was made. I need to know a lot more about the geo locator before I start using it. I can see that if I have my town - parentheses township, it could be a problem because it wouldn't recognize the town. But I can't tell you how many towns I have in my list that it doesn't recognize anyhow. Maybe they are older and the database too updated. I think I'll learn more about using time lines and fill in my own blanks! I do appreciate your input a lot, Paul. Thanks for taking the time! >________________________________ > From: Paula Ryburn <[email protected]> >To: [email protected] >Sent: Thursday, April 26, 2012 9:42 AM >Subject: Re: [LegacyUG] Master Locations - Townships; census > > >Marg, I guess I have been able to determine in each instance whether the >event was in the town or the township. So, I might have two locations in my >location list: Sault Ste Marie, Chippewa, Michigan and Sault Township, >Chippewa, Michigan........ and assign the one that applies. Putting the >township in parens might cause a hiccup in the Geo locator (which I think I >read in another post you have only briefly tried). > > >Also, as another example, I'm sure the city of Chicago was in a "township" or >across several townships (?), but I never try to indicate township for >Chicago... heck, the city takes up the whole of Cook County now (I'm pretty >sure). And to carry that example further, to censuses......... The Chicago >census pages usually indicate in which ward of the city the E.D. lies......... > I will include the "_w7_" in the file name on the image, and I typically add >"(Ward 7)" at the beginning of the Notes field for the census Event. That is, >I do not add the ward to the actual Location field........... although, I >suppose you could. My impression is the ward definitions have changed over >time, so that would just introduce a new level to the issue of a place >changing its place over time............... county boundaries moving, >"Massachusetts Colony," etc, previously discussed here on LUG. I choose not >to add that complexity in the Location list. > --Paula > > ><snip> >Unless I enter it like this: Sault Ste Marie (Sault Twp), Chippewa, Michigan, >United States, I "lose" the information that SSM is in Soo Twp. I think >Barbeau, Chippewa County, Michigan, USA would be in Bruce Twp. (that's a guess >as to the township). I could put the Township in the note field if it the >parenthesis will cause difficulty down the line when I might want to do more >with my data. But as far as I can see this still keeps the four commas for >sorting purposes. > >Another problem arises when the town/city is the same name as the township. >How will I know if the person lived in the town or this is referring to the >township? Since I'm leaving off "County" and just using "Chippewa, it doesn't seem consistent to enter "Soo/Sault Township, Chippewa, MI..." But maybe that is getting too picky. Maybe that is the way it's done. I'm just feeling my way to an entry system with which I'm reasonably comfortable. ><snip> > >Legacy User Group guidelines: >http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages after Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Archived messages from old mail server - before Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >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/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
