Hello,   I used proc geocode 2 years ago with sas 9.4 I think it was TS1M2.   I'm running the same address again using the same street data files that I used 2 years ago, but now I get different results when I do a compare with my new table and the generated table from 2 years ago.  The only difference is that I'm using TS1M3 now.  I'm using the exact same address file and sas street data as last time.   The reason for running it again is to see if there was any changes to the geocode procedure or not.  It seems to have changed and the results now from what I can tell are not as good as last time.  This is based on reviewing a few random addresses.    I am unable to post any of the addresses because they are restricted addresses.  This is what my procedure looks like: proc geocode method = street addressvar = raddr addresscityvar = rcity addressstatevar = rstate addresszipvar = rzip5 data = raw out = raw_geocoded attribute_var = (COUNTYFP, TRACT, BLKGRP, BLOCK) lookupstreet = USM ; run ;     Thank you ... View more

I'm using proc geocode to geocode many addresses.  I have one example where the address says it's a street and zip match, but the M_ADDR value is nothing like the address passed in.  I get a score of 15 for that geocode.  In this case I can't use this data because the X Y values point to the matched address not the original address passed in.  What score or what way can I avoid using the incorrect matched address values?   Here is my geocode: proc geocode method = street addressvar = r_addr addresscityvar = r_city addressstatevar = r_state addresszipvar = r_zip data = addr_raw out = addr_geocoded attribute_var = (COUNTYFP, TRACT, BLKGRP, BLOCK) lookupstreet = geodata.USM ; run ; ... View more