Here's something new: I plotted all of the duplicate points in their own layer -- they are all in a single county, Montgomery County, MD. Could this be a zip code change thing? The 12027 points represent the entire state of MD; the IDs are an autonumber field, entered as data is entered, effectively random geographically, since data doesn't come in by region.
----- Original Message ----- From: "pvillrs" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, April 06, 2005 1:51 PM Subject: [Maptitude] Re: Continued problems with Address Match macro > > > Hello Stan, > > --- In [email protected], "Stan Buck" <[EMAIL PROTECTED]> wrote: >> I checked some of the points which were Not Found manually but > misplaced by >> the macro. They were not among the duplicated points. I couldn't > detect >> any pattern as to which records were geocoded twice. Some were > done > three >> times. > > This really sounds like an id issue. Can you double-check > the values you're using in the field you're using for: 1) the > primary key of the ODBC source, 2) the id field for the > address-matching (these may be the same field, of course). > Again, if there's no obvious problems with your id fields, > can you perhaps send me the database? > > > > > > > > > > Yahoo! Groups Links > > > > > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> What would our lives be like without music, dance, and theater? Donate or volunteer in the arts today at Network for Good! http://us.click.yahoo.com/TzSHvD/SOnJAA/79vVAA/C5grlB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Maptitude/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
