R G, Yes, there are many variations on the theme...
I do want to assure you that you can format the short names. Look at the headers for the GeoXXXCodes.txt files in the Misc folder and you will see something like this: * Special characters + and - mark state/province names to use: * + = Marks the preferred (long) name to use for a state/province. * - = Marks the abbreviated (short) state/province name to use. I run Legacy almost exclusively to show short names. So I setup short names for how I want names to appear in reports, etc. (I have a long standing request to be able to export Short names in Gedcom that I will get one of these days.... ;-)) For example, I could have: Long name: Durham, Durham, England, UK Short Name: Durham, County Durham, England Long name: Boston, Suffolk Co., MA Short Name: Boston, Suffolk County, Massachusetts, United States A lot of trial and error went into the creation of my -Alt files. I still cannot get them to handle Country, State, and County level locations as I want. (I use ____ [4 underscores] for any minor unknown place part; I often have to replace the county with this when the source does not give enough info to identify which county an event took place in.) So I have to create these manually. I always identify a county part as a county (No Boston Suffolk, Massachusetts for me...); I enter US states with their postal codes {sorry, but Bing maps does better with postal codes than state names...); and designate localities with Twp., etc. if that is what source gives. Long Name: ____, ____, ____, France Short Name: France Long Name: ____, Orleans Parish, LA Short Name: Orleans Parish, Louisiana ---> I Geocode Countries to their equivalent of the US Capitol building; States, to the State Capital building, and Counties to the County seat and County courthouse (if I can find it!). john. At 03:30 PM 12/3/2013, R G Strong-genes wrote: >I do that also and once I have both locations geocoded to the correct >location I enter some information in the notes field as a historical date >range of the location and other data as to what it is now. Then I put a >check mark in the verified box so that I know not to delete that location or >combine it with another location of the same name. Also be aware that you >can have more than just 4 comma delimited places upto 9 ie for a cemetery I >have: >cemetery, city, county, state, country >If it did not auto code to the right place then I can then put that in the >geo location database editor and if it finds the Core city, county, state, >country I select the Core + button and the place is then formatted to how I >have the geo - alt text files set up for that location. ie I enter the full >country name and have it format the short names: United States to USA. I >have not found a way for the auto geocode to format the short location >names, so I usually just edit any new locations with the geo locations >database and make sure that I tick the current geocodes and not the new >geocodes that it finds for the city but uses the one that I placed for the >core + location. Once it is formatted how I want I can usually find the >place I want and move the pin to it. If I can't find the location I will >google the location and usually find it in a google map and compare it to >the bing map and usually find it by other landmarks that are on the google >map. > >-----Original Message----- >From: John B. Lisle >Sent: Tuesday, December 03, 2013 2:25 PM >To: LegacyUserGroup@LegacyUsers.com >Subject: Re: [LegacyUG] Geobase international location questions > >Pam, > >Please indulge me to talk about Location in >Legacy 8. Actually, little has changed since >Legacy 7 but many users do not have a strategy >for locations and mapping and such. > >--> One of the major changes (and it is rather >minor) for L8 is that the GeoDB is now unified. >Instead of picking and choosing which regions you >want, you get to install a file that has all >regions. The file is a large download but it is >about the same size as the program installer file >so it should be no more of a problem to download. >Everyone should want to download and install this for L8. > >Legacy has 2 tools for Geo Coding your locations. >Unfortunately, both operate, more or less, based >on current place names, not historical place names. > >The strategy I use for a historical name is to >determine what the name of the place is now and >use the Bing map to find it. And, if that does >not work, try to find it with the GeoDB. > >---> The GeoDB can be made to format the name of >a location with great flexibility using the >GeoCode-alt.txt files, but that is another lessone.... ;-) > >Then, if found, go back to the Bing Map to use >more precise right click placement. > >--> Sometimes, neither works. This is when I go >to Wikipedia or Google to have one of them try to >show me where the place is. Then "transfer" those >coordinates to Legacy. I will make a lot of use >of the Bing satellite views to try to place the >pin at the most favorable location. > >Once I have the location resolved, I will then >create a new location with the historical name, >prefixed by the current name. When editing the >name, I check the box that says do not automatically geocode. > >Then I go to the present day location, showing >the pin where the place is, then move to >historical named place and right click the pin to >the same place. Then edit the location to remove >the prefix new name which I only added so the two >places were next to each other in the place list. > >This may sound confusing, but once you have done >it once or twice it becomes easy. And you can >figure out shortcuts to the process. > >I have done 1000s of locations using these techniques. > >Please note that the Bing maps can give a more >precise location than the GeoDB. But the GeoDB is >a great tool for assuring that the location name >is constructed correctly and all of the parts are spelled correctly. > >For most US, Canada, and UK locations, the less >info you give Bing, the better it does. IE, >adding a county will often confuse it. For US, it keys off of City and >state. > >OK? > >Do you have more questions? > >john. > >At 12:25 PM 12/3/2013, Pam Gosling wrote: > >Hello, > > > >I there any recommended format to list locations > >for the older Prussian now Pommeranian areas of > >former Germany now Poland? Iââ¬â¢m new to this, >, > >and in the archives from 2010, it seems that it > >is not possible for the Geobase to properly > >identify these locations? à So, if this is true, are these my only > >options?: > > > >1. Just not use the geobase feature and > >list the location as well as possible? > >2. Look up lat/long date from online maps > >and insert to program? Or does that even work? > >3. Another idea? > >4. If I do add lat/long to database, does > >that get saved for others to use? Or just my file? > > > >If there is no way to use this mapping feature > >for international locations, is there a standard > >recommended format for myself to list, just so I have the proper format > >anyway: > > > >For example: > > > >Zeitlitz, Kreis Regenwalde, Pommerania, Prussia (old German ) > > > >Which is now in: > > > >( town Polish not yet translated), > >Resko(Regenwalde), Lobez(ââ¬à âlike countyââ¬Ã > > >missing the Poland diacritical mark), Poland > > > >e.g. should I write either the (old) or > >new/current names in parentheses/inside > >brackets, with hyphens, or only list the current > >names and describe older German names in notes or something? Or what? > > > >And, is there a way to import the Polish > >diacritical letters(?right way to describe > >them?); they are not included in the options I > >can click on. When I tried to paste one to the > >family name in the address location field, it > didnââ¬â¢t keep the mark. >. > > > >I want to write the locations in such a way so > >that in the future if the mapping function for > >international locations ever comes about, I > >donââ¬â¢t want to have to rewrite all of these. >. > > > >And, Iââ¬â¢m assuming this applies to both >h > >ââ¬à âeventsââ¬Ã such as residence, and the address >s > >field for births, deaths, etc? Or would that make a difference? > > > >Thanks so much for all the gracious help on this list; very appreciated.à > >Pam > > > > > >-- >Russell G. Strong >P. S. Check out Legacy Family Tree today! This full featured genealogy >program can be downloaded FREE at >http://www.legacyfamilytreestore.com/Articles.asp?ID=133&Click=1114 >Oh so many branches and not enough time to check out all the roots!!!. >Check out my Genealogy Pages at http://www.rgstrong-genes.com . > > > > >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