I find that the structure of some events results in an excessive number of locations that cannot be resolved by geo-location. For example the location of many marriages is reported in the marriage license as "at the home of so and so [usually father of the bride], actual address". Many deaths take place at "Such and such Hospital, address". Geo-location cannot resolve these because it does not know to ignore everything from the beginning to the first comma. These extra entries complicate the auto-complete function for locations. For example I have a frequently used "location" of "Ontario Psychiatric Hospital, London, Ontario, Canada". Whenever I want to specify that an event took place in Ontario, Canada, I have to type almost the whole location before auto-complete works, because space sorts before comma. Also I end up with a lot of semi-duplicate entries in the locations master list, which in my database currently contains 18,088 entries. I wish that I could separate the description of the location from the actual location while not affecting how the complete value is displayed to users. That caveat makes the option of putting the description into the marriage notes less than satisfactory.
I would appreciate your thoughts on this. 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
