I am thinking that the person who said something should be developed using the longitude / latitude coordinates to tie them in to every location name really has a great concept for the programmers to consider for a future update.
But that being said, Julia, just for your benefit, if the four-division fields are used (or some other standard practice of total consistency), you come out a lot better if you plan on sharing gedcoms or putting your information on a website. For example, on our website, because I use the 4-fields, when one goes to the place names, it will display initially with the COUNTRIES of the world similar to the following: USA - 1,442 locations CANADA - 612 locations etc. Then when you click on USA, you will get: Alabama, USA - (11) Alaska, USA - (4) etc. Then when you click on Alabama, you will get: Alabama, USA (6) Colbert Co, Alabama, USA (2) Jefferson Co, Alabama, USA (1) Lauderdale Co, Alabama, USA (1) Montgomery Co, Alabama, USA (1) Then, for example, if you click on COLBERT COUNTY, you will get: Muscle Shoals, Colbert Co, Alabama, USA Sheffield, Colbert Co, Alabama, USA Then when you click on the icon at the end of Muscle Shoals, it will show you every person's record where Muscle Shoals is referenced and on down the line. You can do very similar things with Legacy itself by using the powerful sorting features in which you can isolate any of the fields (actually up to 9 if you want to take it that far). So, just bringing this to your attention for you to be able to see how well the four-division system works in LEGACY when you transfer the same identical information to a website that has a system that will accommodate it. I don't think you will be able view your master location lists with as much versatility unless you have a complete consistency in the way you input your locations. PS--On the public side of our website, you will see pretty much the same thing except it is not complete yet and some corrections are needed. But if you contact me, I can allow you access to the entire site. Thanks, Jerry Boor - MerriamFamilyTree.org On 11/20/2011 7:38 AM, M. Brenzel wrote: > Kirsten, > > Very well said. This is a “battle†that has been raging off and on for > a long time. I’m on the side of putting everything into the location > field, including the names of hospitals, schools, and cemeteries. Even > with that, my longest location field is only 7 parts. Works quite well > when the Master Location List is sorted right to left. > > Mary > > *From:*Kirsten Bowman [mailto:[email protected]] > *Sent:* Sunday, November 20, 2011 12:43 AM > *To:* [email protected] > *Subject:* Re: [LegacyUG] Locations > > Julia: > > It seems you’re getting quick partial answers to your initial question > because it’s a very complex issue. Legacy is basically designed to work > with a 4-part location field consisting of City, County, State, Country > but it will accommodate much more (or less). If any of those four > elements are missing you can add placeholder commas to flag the missing > data. The benefit to this system is that it will work well in > conjunction with some other features such as mapping. > > There are also downsides to the 4-part location arrangement which you’re > seeing now. Many users dislike the way placeholder commas appear in > reports; lots of people like to include full street addresses in the > location field which aborts the City, County, State, Country format to > some degree; frequently you can have a perfectly legitimate location > containing fewer than four elements—or many more than four; and > sometimes you may have a location like “New York†and need to identify > whether it’s the city or the state, or you could have “(at) Sea, > Atlantic Ocean.†> > Legacy is very versatile. You can put just about anything you want in > the Location field and it will transfer in a GEDCOM without a problem. > Most of us have tried various location data entry styles and picked the > one(s) that work best for whatever we want to produce whether it’s a > website, specific report, map, or whatever. There are many (and > conflicting) *recommendations* about how to use the Location field but > there are no set *rules*—only consequences associated with one method or > another. > > Experiment with some of the options and see how they work for you. If > you eventually decide you want to change the style it’s very easy to do > global changes from the Location List. > > Kirsten > > *From:*julia _ <mailto:[email protected]> > > *Sent:*Saturday, November 19, 2011 1:42 PM > > *To:*[email protected] > <mailto:[email protected]> > > *Subject:*RE: [LegacyUG] Locations > > I guess I don't understand where is the harm from adding the word > county. Does this mess up my Gedcom should I choose to submit one > somewhere/to somebody? > > Julia > > ------------------------------------------------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: [LegacyUG] Locations > Date: Sat, 19 Nov 2011 12:57:07 -0800 > > “, how do I know that the first word is the name of the county and not > the name of a city?†> > You don’t, that is why I always ADD the word County in ALL cases. I > think it is just plain stupid that these mapping sources have gone to > this method. If one does NOT know about this method, then they will not > know if it is the City or County that is being used. > > Thanks, > David C Abernathy > Email disclaimers > ---------------------------------------------------------------------------- > This message represents the official view of the voices in my head. > ---------------------------------------------------------------------------- > http://www.SchmeckAbernathy.com <http://www.schmeckabernathy.com/> > == All outgoing and incoming mail is scanned by F-Prot Antivirus == > > > > 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 > > > > 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
