Stan,
I my experience, if you want to increase the hit rate when geocoding wth
Maptitude, you need to do some pre and post processing before calling
any of the Standard Interface Macros (""GISDK Locate Address" and
"GISDK Address Match"). That means using some GISDK routines in order
to have a better control of the process.
Armando
Stan Buck wrote:
>I have to ask this again because I never got an answer the first time, but
>the problem is growing.
>
>When we geocode our database, there are always some addresses that are on
>streets that are too new to be in Maptitude's Streets database. If I
>geocode the database manually, i.e. open the file, choose
>Tools-->Locate-->Locate by Address, these addresses are properly marked Not
>Found.
>
>But if I try to do it in GISDK code using the Address Match macro:
>
>RunMacro("GISDK Address
>Match",vw1+"|",{"recordID","address","zip",},"Streets",strDBPath,"Child
>Care",)
>
>the macro seems to attempt to guess the location of the point. They are
>given incorrect lat/longs. Sometimes it's obvious what was going on, i.e.
>an address on Weeping Cherry was plotted on Cherry Lane, 2 miles away, but
>usually it's not apparent what the program is doing.
>
>We would rather have these addresses Not Found than incorrectly plotted.
>How can I geocode with GISDK without this happening?
>
>Stan Buck
>
>
>
>
>
>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/
