[AccessD] Address Recognition

Reuben Cummings reuben at gfconsultants.com
Fri Jun 15 15:12:32 CDT 2007


It'll be ongoing.  Reports are released weekly from the BMV - one for each
county (92).  And every county has to process them separately.  That's
roughly 4,800 reports per year.

It needs to be something that can run from within my app and the user
basically doesn't know it exists.

If your friend is willing I'd love to talk to him.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Mark A Matte
> Sent: Friday, June 15, 2007 4:01 PM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Address Recognition
>
>
> Reuben,
>
> I have a friend that does this type of work.  He uses a number of
> different
> tools(some purchased...some he built).
>
> Will you need this ongoing or just once?  Outsourcing to an 'Address
> Standardization' company might be an answer.
>
>
> Good Luck,
>
> Mark A. Matte
>
> Also...I think JC just went through this exercise...
>
> >From: "Reuben Cummings" <reuben at gfconsultants.com>
> >Reply-To: Access Developers discussion and problem
> >solving<accessd at databaseadvisors.com>
> >To: "AccessD" <accessd at databaseadvisors.com>
> >Subject: [AccessD] Address Recognition
> >Date: Fri, 15 Jun 2007 15:41:09 -0400
> >
> >I have an app that loads BMV records from the state.  In those
> records are
> >the auto owners home addresses.  Unfortunately, the addresses are listed
> >completely in one field.  For example 485 1/2 Ferry St or 676
> Ferry Street.
> >
> >I need to go thru this entire list upon importing from the state and set
> >every record to its proper taxing unit which is entirely based upon the
> >address listed.  If no address is listed I will simply indicate
> the taxing
> >unit as Unknown and the user will check manually.
> >
> >My biggest problem is illustrated by the following address (real
> data from
> >a
> >client)...
> >91 Antioch
> >60 Antioch Lane
> >12 Antioch LN
> >6 Antioch RD
> >300 Antioch Road
> >
> >These may be one, two, or three different roads.  Either way there are 5
> >variations that must be analyzed.
> >
> >Anyone have any good functions or suggestions for reading these addresses
> >and assigning units?
> >
> >I plan to make a table that will allow the user to define the road names,
> >address ranges, which sides of the road belong in a taxing unit.  My
> >problem
> >is how do I handle all the variations of a road?  Should I force them to
> >simply add more road definitions or is there a way to "Very Accurately
> >Guess" what road it should be?
> >
> >Also, how do I handle a road number like 485 1/2 Ferry St.
> Val([Address])
> >returns 4851 which results in a Street Name being /2 Ferry St.  I need to
> >analyze and handle the 1/2 portion of this address as well.
> >
> >I am currently working on this with a few counties, but plan to meet with
> >the state BMV to try to make it the default processing software for ALL
> >counties in Indiana.
> >
> >Any and all help greatly appreciated!
> >
> >Reuben Cummings
> >GFC, LLC
> >812.523.1017
> >
> >
> >
> >--
> >AccessD mailing list
> >AccessD at databaseadvisors.com
> >http://databaseadvisors.com/mailman/listinfo/accessd
> >Website: http://www.databaseadvisors.com
>
> _________________________________________________________________
> Make every IM count. Download Messenger and join the im Initiative now.
> Its free. http://im.live.com/messenger/im/home/?source=TAGHM_June07
>
>






More information about the AccessD mailing list