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] Sent: Thursday, March 22, 2012 4:31 PM To: 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> 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 > > 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 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
