Please carefully read my post. I am not expecting Millennia to make VE more accurate. I only want Legacy to not overwrite entries that have already been looked-up or hand-entered without at least a question to the user as to whether that VE information should be stored instead of what is already in the table. And the same should be true of any other new information that might overwrite something already recorded.
You are absolutely correct about Microsoft being responsible for the accuracy of the info they provide via Virtual Earth as would any other provider of mapping information. I experimented today with several locations to see what VE would do with them. Some were not even found as would be indicated by the balloon on the map but still Legacy put in the "V" in the column with a generic latitude and longitude of the general location of that item. Sometimes it would put in a spot somewhere in the county or even the center of the state. This is not helpful. If a specific town cannot be found, then the "V" and other info should not be stored. Ron Taylor --- On Sun, 9/19/10, Ron Bernier <[email protected]> wrote: > From: Ron Bernier <[email protected]> > Subject: Re: [LegacyUG] Places > To: [email protected] > Date: Sunday, September 19, 2010, 12:01 PM > You do realize of course, Millennia > has absolutely no control over Virtual > Earth. Legacy is merely providing a "link" to a > mapping tool. Any > complaints about how virtual earth works needs to be > addressed to Microsoft. > Microsoft is the only one who has control over the > inaccuracies. > Ron Bernier sent from my Verizon BlackBerry > > ----- Original Message ----- > From: Ron Taylor <[email protected]> > To: [email protected] > <[email protected]> > Sent: Sun Sep 19 12:21:52 2010 > Subject: Re: [LegacyUG] Places > > This "mapping" problem needs to be addressed (pun > intended). I have found > many locations that are found with Virtual Earth to be > inaccurate. Your > example of a town out-to-sea is a good one. I am > especially troubled when a > location that has been accurately determined by a call to > the GEO database > is allowed to be overwritten by a find on Virtual Earth > which is different > and wrong. If a location has "L" in the L column to > indicate that it has > been looked-up in the GEO database, then when Virtual Earth > finds it, there > should at least be a question whether the L should be > changed to a V and the > Virtual Earth information allowed to replace the GEO > database info. The > same logic should probably apply when a GEO database lookup > wants to > overwrite info from Virtual Earth. Even if the user > has hand-entered a > location's coordinates, that info should not be replaced > automatically by a > Virtual Earth or GEO database lookup. > > It would be very interesting to see a comparison of a > locations list that is > all sync'ed with GEO database versus the same list sync'ed > with Virtual > Earth and compute the difference in distance between the > same locations. > > Try doing a GEO database lookup on a location that already > has V in column L > and see if you can get the program to put L in that > column. > > Last point on this mapping. When the program does > find a location and > identifies it on the map with a balloon...the point of the > balloon should > indicate the coordinates and not the center of the > balloon. It would also > help to have the balloon be translucent so items it covers > could be viewed. > > Ron Taylor > > > > > > > > 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 > > > > 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 > > > > 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
