Yes, a RunMacro statement to automate the geocoding process:
RunMacro("GISDK Address Match",vw1+"|",{"recordID","address","zip",}etc
Our databases change daily and must be re-geocoded each time, so automating
the process is important.
When I do it by hand, the addresses return a "RSS" code, using the method
you outlined.
Stan
----- Original Message -----
From: "Aniruddha Banerjee" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, January 17, 2005 6:33 PM
Subject: Re: [Maptitude] Geocoding non-existant addresses
>
> I'm sorry for responding late but could you elaborate on the process
> you are following? Are you using A GISDK macro? Regards, R.
>
>
> On Thu, 13 Jan 2005 15:18:04 -0500, Stan Buck <[EMAIL PROTECTED]>
> wrote:
>> When I do this (geocoding manually), these addresses are not found, even
>> at
>> Not Strict setting. But they are when the Address Match macro geocodes
>> them. How do I adjust the macro?
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Aniruddha Banerjee" <[EMAIL PROTECTED]>
>> To: <[email protected]>
>> Sent: Thursday, January 13, 2005 1:03 PM
>> Subject: Re: [Maptitude] Geocoding non-existant addresses
>>
>>
>> >
>> > Use the following menu item before you geocode:
>> >
>> > Tools-Locate-Locate by Address-Address(tab)-Mathing Method-Very
>> > Strict(scroll down);
>> >
>> > The default method is 'Normal'.
>> >
>> > Also, check the 'Save Standardization' box. Adbf file is created that
>> > has a column with details of what type of "strictness" was used (see
>> > below). Select the ones that make the best sense. This AI approach to
>> > geocoding from Caliper is superior to any other I have seen in the
>> > industry.
>> >
>> > Code What it means...
>> >
>> > A The record was located successfully, without asking you for help
>> > R The record was not located automatically
>> > U Maptitude offered you several possible matches, and you chose one
>> > X Maptitude offered you several possible matches, and you rejected them
>> > all
>> > I The input address was identified as an intersection
>> > S The street name or alternate name did not match exactly
>> > N The street number did not match exactly
>> > Z The input ZIP Code was not found in the Streets file
>> >
>> > Match Result What it means...
>> > A The record matched a street feature perfectly and was located
>> > automatically
>> > AS The record was located successfully, even though the street name
>> > did not match perfectly
>> > US The street name did not match perfectly, Maptitude offered you
>> > several choices, and you accepted one of them
>> > RSN The record was not located because neither the street name nor the
>> > street number matched
>> > RSSN The record was not located because the street name, the alternate
>> > street name, and the street number did not match
>> > AI The address was interpreted as an intersection, and was located
>> > automatically
>> > etc...
>> >
>> >
>> > On Thu, 13 Jan 2005 10:12:19 -0500, Stan Buck <[EMAIL PROTECTED]>
>> > wrote:
>> >> We have a couple of points on Weeping Cherry Ct. However, Weeping
>> >> Cherry
>> >> isn't in the streets database -- it's too new, whole development just
>> >> a
>> >> couple of years old. But Maptitude does geocode these points -- on
>> >> Cherry
>> >> Lane, about 2 miles away. Evidently it's making its best guess. I'm
>> >> using
>> >> the Address Match macro; is there any way to suppress this behavior?
>> >> Rather
>> >> have the geocoding fail than have points in the wrong place.
>> >>
>> >>
>> >>
>> >>
>> >> ________________________________
>> >> 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 the Yahoo! Terms of Service.
>> >
>> >
>> > --
>> > Aniruddha Banerjee, Ph.D.
>> > Associate Research Scientist
>> > Prevention Research Center
>> > 1995 University Ave, Ste 450
>> > Berkeley, CA 94706
>> > 510.883.5740
>> > fax 510.644.0594
>> >
>> >
>> >
>> >
>> > Yahoo! Groups Links
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>> ________________________________
>> 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 the Yahoo! Terms of Service.
>
>
> --
> Aniruddha Banerjee, Ph.D.
> Associate Research Scientist
> Prevention Research Center
> 1995 University Ave, Ste 450
> Berkeley, CA 94706
> 510.883.5740
> fax 510.644.0594
>
>
>
>
> 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/
