[postgis-users] Geocoding Issues with Route, ##-## house numbers; upgrade questions
Paragon Corporation
lr at pcorp.us
Wed Jul 27 23:31:38 PDT 2011
Steve,
Thanks. I would be interested in this once I get to tackling street
numbers, but battling some other issues at the moment on various other
fronts so I'm a bit distracted and only focusing on low hanging fruit aside
from the critical stuff I'm working on.
Thanks,
Regina
> This is a harder problem because there are a great many different house
> number range patterns and most geocoders assume only simple house
> numbers. This problem is compounded by the fact that you need to match
> even if one or more of the components are missing. For example, if the
> street has an address range does the 112 or the 31 component vary over
> the range?
> Regina, If you want all the various patterns I have what so other docs
> that have all the patterns described. We might also want to load all the
> Tiger data and run a pattern classifier on all the Tiger house numbers.
> We could convert the actual house number into something like:
> n - a string of digits
> a - a string of letters
> p - punctuation
> s - space(s)
More information about the postgis-users
mailing list