I should have added that within the Workspace being used, I have "Inset address" from end of street set to zero as these are mainly rural streets set to 0.001 mile addressing format.
Find Using Streets(COL1) Refine Using Communities(COL1) Options Abbrs Off ClosestAddr Off OtherBdy Off Symbol Inset "0" Distance Units "ft" Offset "15" Distance Units "ft" When I plot the two addresses (that have come to our attention) in Mapinfo, they geocode right where their supposed to. Thus far, all other addresses that have been searched appear where their supposed to. Additionally, the tables being used are maintained in MI 6.5, but the Proviewer we're using is 6.0. I would think that would be an issue though. Strange indeed Dave -----Original Message----- From: Bill Thoen [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 27, 2006 9:08 AM To: David Reid Cc: [email protected] Subject: Re: [MI-L] Strange "Find" results geocoding in MI ProViewer On Tue, Jun 27, 2006 at 08:42:57AM -0500, David Reid wrote: > Yesterday, on various addresses entered to the "Find" dialog, it started > geocoding some of these addresses as much as 1/2 mile from where the address > is known to accurately geocode otherwise. > > Has anyone seen this before and found what causes this problem? Are these addreses supposed to be near the start or end of a long rural road? MapInfo's algorithm moves addresses near a road intersection back up the road about 10% of the length of the segment. This keeps the locations from "bunching up" on intersections in the cities, but it's not helpful in the country. I think there's a preference setting for this somewhere. -- Outgoing mail is certified Virus Free Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.5/376 - Release Date: 06/26/2006 _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
