VB .NET has a regular expression engine which is much the same as PERL's. It is far, far more efficient than using MID, LEFT, RIGHT, INSTR, etc. in VB or VBA.
Dave
Bill Thoen wrote:
>I'm looking for advice and algorithms for splitting US addresses into >street number, prefix direction, street name, street type, suffix >direction and unit. The problem I have is that the addresses I'm working >with have all these logical fields combined into one physical field and >the elements are not standardized. For example, the information in the >street field may vary a lot. There may or may not be direction information >or even street types. You can't be sure that the second word represents >the prefix direction, and it's really hard to tell which word is the last >one of the street name and whether the next word is the street type, >suffix direction or unit. Also some street names are spelled differently, >like "Woody Creek Rd" and "Woody Crk Rd." > >Any suggestions on how to approach this problem? I'm currently working on >this in an Access database, and I can handle SQL and VBA programming >without too much difficulty. I'm just wondering how big a problem this is, >and how to break it down into smaller problems. > >I did find some general articles on street elements via Google, and I know >where to get the USPS abbreviations for street types and directions, but I >haven't found any technical details on how to parse and standardize >addresses, so before I try to start from scratch, I thought I'd ask and >see what ideas and pointers that others might have. > >- Bill Thoen > > > _______________________________________________ gislist mailing list gislist@lists.geocomm.com http://lists.geocomm.com/mailman/listinfo/gislist
_________________________________ This list is brought to you by The GeoCommunity http://www.geocomm.com/
Get Access to the latest GIS & Geospatial Industry RFPs and bids http://www.geobids.com
|