Re: MI Geocoding problem
Sarah, First of all, look at the fallback. Might say to ZIP only. 2nd, look at the georesult. Might say N or ND for no data. Either the wrong CD, or not unlocked property (happens). 3rd, try geocoding in interactive mode. This will allow you to see how the columns are matched, etc. Good luck. Dan Munson CDS Business Mapping - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 25, 2000 2:01 PM Subject: MI Geocoding problem > Hi all - I don't understand what is happening (no I am NOT blonde!). I just > added a new site to my master table of my California CUC sites. I added the > site name, address, zip code - however when I re-geocoded the table it only > locates it to the Z1 - the zip centroid. I checked my MapMarker Plus Streets > CD and found the street name. Anybody have any insite why isn't it finding it > when it geocodes? For that matter I have about 12 sites that geocode to the > Z1 when the street name exits. > > PS to John Hoffmann - I LOVED your Friday Humor! > > <;)))>< > Sarah Myers > > Blessed are they who can laugh at themselves > for they shall never cease to be amused. > -- > To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put > "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI Geocoding problem
Hi all - I don't understand what is happening (no I am NOT blonde!). I just added a new site to my master table of my California CUC sites. I added the site name, address, zip code - however when I re-geocoded the table it only locates it to the Z1 - the zip centroid. I checked my MapMarker Plus Streets CD and found the street name. Anybody have any insite why isn't it finding it when it geocodes? For that matter I have about 12 sites that geocode to the Z1 when the street name exits. PS to John Hoffmann - I LOVED your Friday Humor! <;)))>< Sarah Myers Blessed are they who can laugh at themselves for they shall never cease to be amused. -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
RE: MI geocoding problem
Alex, If you have a road dataset that includes the zipcode as an attribute and you have the zip code in the addresses perhaps you could do a series of geocoding zipcode by zipcode eg 1) - get list of all zip codes (eg select zipcode from streettab group by zipcode) 2) - select all roads with the first zipcodes (eg select * from streettab where zipcode = "ABC" into touse_road) 3) - select all address with the same zipcode (eg select * from address where zipcode = "ABC" into todo_add) 4) set your geocoding preference to use just the selected datasets eg Find Using touse_road(add_col) 5) geocode the todo_add table 6) get the next zipcode and repeat from 2).. this code be relatively straight forward in mapbasic but if you are doing it manually may be a bit combersome. Also record the return value from the Find statement so that you can check the accuracy of the match at a later time. Cheers Martin == Martin Roundill GIS Manager Waitakere City Council Private Bag 93109 Henderson Waitakere City New Zealand -Original Message- From: Alex Chen [mailto:[EMAIL PROTECTED]] Sent: Friday, 21 January 2000 09:17 To: [EMAIL PROTECTED] Subject: MI geocoding problem Hi- we have 40,000 addresses that we would like to automatically geocode. We have the street address, which are not always accurate, as well as it zipcode, which we are comfortable with. The problem is that sometimes the address is incomplete, e.g. 100 winchester rather than 100 n winchester. Automatic geocoding doesnt pick up winchester, further there is a 100 n winchester and a 100 s winchester, and we are uncomfortable with arbitrarily picking south or north. My question is, Is there a way to take advantage of the zip code we have, i.e. if we know the zipcode, we know the general area, and can exclude parts of winchester - something like that. we are using 5.0 (but can install 5.5). we use mapinfo streetpro. thanks for any ideas suggestions. -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
RE: MI geocoding problem
Alex, There are two ways to do this. 1. Use a ZIP code layer to act as a boundary layer. If the geocode result is not in the matching zip, it will not geocode. This does not put in the right place, but it at least eliminates some bad geocodes. The manual shows how to set this up. 2. Get MapMarker. MapMarker has a database of every address in the US (or your state) and will attempt to correct the address you give it and match it to an existing address before doing the geocode process. This address scrubbing greatly improves geocode results. But remember the golden rule of computers: Garbage In = Garbage Out. You are dealing with imperfect addresses and an imperfect street base. You will get imperfect results no matter what you do. 100 N Winchester always geocodes incorrectly because the address ranges on all tiger based street layers are wrong for this area. BTW, where are you guys at? Our address is 100 N Winchester in Santa Clara, CA. - Brad > -Original Message- > From: Alex Chen [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, January 20, 2000 11:10 AM > To: [EMAIL PROTECTED] > Subject: MI geocoding problem > > Hi- we have 40,000 addresses that we would like to automatically geocode. > We have the street address, which are not always accurate, as well as it > zipcode, which we are comfortable with. The problem is that sometimes the > address is incomplete, e.g. 100 winchester rather than 100 n winchester. > Automatic geocoding doesnt pick up winchester, further there is a 100 n > winchester and a 100 s winchester, and we are uncomfortable with > arbitrarily picking south or north. My question is, Is there a way to take > advantage of the zip code we have, i.e. if we know the zipcode, we know > the general area, and can exclude parts of winchester - something like > that. we are using 5.0 (but can install 5.5). we use mapinfo streetpro. > thanks for any ideas suggestions. > -- > To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put > "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI geocoding problem
Hi- we have 40,000 addresses that we would like to automatically geocode. We have the street address, which are not always accurate, as well as it zipcode, which we are comfortable with. The problem is that sometimes the address is incomplete, e.g. 100 winchester rather than 100 n winchester. Automatic geocoding doesnt pick up winchester, further there is a 100 n winchester and a 100 s winchester, and we are uncomfortable with arbitrarily picking south or north. My question is, Is there a way to take advantage of the zip code we have, i.e. if we know the zipcode, we know the general area, and can exclude parts of winchester - something like that. we are using 5.0 (but can install 5.5). we use mapinfo streetpro. thanks for any ideas suggestions. -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
