Until the organic act, the District was made up of two counties and three towns ....Washington and Alexandria counties, and the communities of Washington, Georgetown and Alexandria so until the mid 1870s it plots out just as it would for any other location with the District in the state slot.
Of course Alexandria and the "Virginia" portion of the District were ceded back to Virginia - and at some point (I forget exactly when) Georgetown was merged into Washington. Washington county was dropped and the District became its own county. And that is when things don't look as if they fit into the norm. I have quite a few D.C. families from its founding and settlement in the 1790s to the early 1900s. They are an interesting lot to find because many of their records never ended up within the District in the first place. Many preferred to file many of their formal papers in the adjoining Maryland or Virginia counties which presents its own problems when trying to indicate that while a will was filed in Montgomery county for an example, they were actually D.C. residents. Now what about the U.S. territories? How do those read? I actually have a couple of those to deal with. Jackie On 3/23/2012 6:33 AM, Michele Lewis wrote: > > I have never used Washington DC as a location so I looked to see howit > would geocode. > > Fairfax Village, District of Columbia, District of Columbia, United States > > Michele > > *From:*David C Abernathy [mailto:da...@schmeckabernathy.com] > *Sent:* Thursday, March 22, 2012 8:02 PM > *To:* LegacyUserGroup@LegacyUsers.com > *Subject:* RE: Re: [LegacyUG] Pesky location list > > We also have a place here in the US that is a City only, NO County, NO > State, Washington, District of Columbia, so now where are the extra > coma going to be, as there should be NONE? > > 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 == > > *From:*sarlesinsi...@gmail.com <mailto:sarlesinsi...@gmail.com> > [mailto:sarlesinsi...@gmail.com] > <mailto:[mailto:sarlesinsi...@gmail.com]> > *Sent:* Thursday, March 22, 2012 4:31 PM > *To:* LegacyUserGroup@LegacyUsers.com > <mailto:LegacyUserGroup@LegacyUsers.com> > *Subject:* Re: Re: [LegacyUG] Pesky location list > > I suspected something like that. So, the total is 4 places and if you > have the state and the country, you need two commas, with 1 space between. > > Thanks. > > Jane > > On , Brian/Support <br...@legacyfamilytree.com > <mailto:br...@legacyfamilytree.com>> wrote: > > Jane, > > > > > > > > The Expand/Contract locations insists that the format be four levels > > > > city, county, state, country > > > > If any part is missing that part must be replaced with a comma > > > > Your examples below are correct but you should also use > > > > city, , state, country if the county is missing and > > > > city, , , country if the county and state are missing. > > > > > > > > The country can be missing without a replacement comma and, if the > > > > location is in the United states Legacy will recognize the state name > > > > and know that the place is in the USA. > > > > > > > > In your earlier email the problem places were not in the correct format > > > > Guilford Co., NC was missing the comma for the missing city > > > > , , , Alabama has too many commas before the state name > > > > , , Fluvanna County, Virginia, also has too many commas before the > > > > county there should only be one. > > > > > > > > Brian > > > > Customer Support > > > > Millennia Corporation > > > > br...@legacyfamilytree.com <mailto:br...@legacyfamilytree.com> > > > > http://www.LegacyFamilyTree.com > > > > > > > > We are changing the world of genealogy! > > > > When replying to this message, please include all previous > correspondence. > > > > Thanks. > > > > > > > > On 22/03/2012 3:03 PM, sarlesinsi...@gmail.com > <mailto:sarlesinsi...@gmail.com> wrote: > > > > > Is this the recommended format for locations? I have tried and > failed to > > > > > find exactly the correct way to input locations when various parts are > > > > > known. > > > > > > > > > > , , Virginia, United States > > > > > , Albemarle County, Virginia, United States > > > > > Anytown, Albemarle County, Virginia, United States > > > > > > > > > > I am working toward getting the automatic fill-in thing to work in my > > > > > Legacy program. It does not now work. > > > > > > > > > > Jane Sarles > > > > > > > > > > > > > > > > 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 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
