[AccessD] Address Recognition

Reuben,

  Only way I've ever found to deal with this is simply a brute force
approach.

  I take the string, split it up into an array, determine the number of
parts, then try and figure out what the address should be.  

  It's probably not as bad as you think.  Should not take more then a few
hours to set something up and work the kinks out.

Jim.

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben Cummings
Sent: Friday, June 15, 2007 3:41 PM
To: AccessD
Subject: [AccessD] Address Recognition

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