RE: [LegacyUG] Another example

2012-02-24 Thread Michele Lewis
Thanks for confirming it, Jenny. I didn't want people to think I was completely daft :) michele There's something odd going on. I opened Bing Maps outside of Legacy and tried to plot Marshall, Alabama, USA. Bing produced several locations around Birmingham, Alabama but did not find Marsh

Re: [LegacyUG] Another example

2012-02-24 Thread Jenny M Benson
On 24/02/2012 14:02, Michele Lewis wrote: > Here is another example… > > , Marshall, Alabama, USA > > Shows up east of Amherst, NY > > I am letting Legacy geocode these,I am not doing it manually. There's something odd going on. I opened Bing Maps outside of Legacy and tried to plot Marshall, A

Re: [LegacyUG] Another example

2012-02-24 Thread Ron Ferguson
: [LegacyUG] Another example I do remember when google maps first came out and you could include a small map on your website, if the marker pointed to the wrong place, google had a way for you to move it and report back the 'fix' to them. Does Bing do that? (granted, my experience was it was p

Re: [LegacyUG] Another example

2012-02-24 Thread Paula Ryburn
rdle Jones Klein Koyle Laswell McDonald Misner Passwaters Pelton Roberts Roche Ryburn Sanford Short Singer Sullivan Weller Williams From: Sherry/Support To: LegacyUserGroup@LegacyUsers.com Sent: Fri, February 24, 2012 9:47:02 AM Subject: Re: [LegacyUG] Anoth

Re: [LegacyUG] Another example

2012-02-24 Thread Sherry/Support
But if you're geo-coding through Bing, then Big should locate the place correctly. We're aware that corrdinates in Geo Location Database are not always correct and unfortunately, there's nothing we can do about it since it came from another company. I have worked with users who have reported probl

Re: [LegacyUG] Another example

2012-02-24 Thread Gene Young
On 2/24/2012 9:02 AM, Michele Lewis wrote: > , Marshall, Alabama, USA The problem lies in the database that Legacy uses for Geo-locating. Some of the locations have incorrect latitude and longitudes entered and therefore locate the wrong place. It is a Legacy problem, insofar as Legacy uses a cor