My question is already answered: someone committed changes at http://trac.osgeo.org/postgis/ticket/1333#comment:3.
Are these already in the SVN trunk? Aren On Wed, Nov 30, 2011 at 6:29 PM, Aren Cambre <a...@arencambre.com> wrote: > Based on the conversation below, it appears there is already a solution, > and people well-versed with PostGIS may be helping with this already. Given > that, are my n00b skillz of much use? > > Second question--when might this cross street feature be available? I am > asking for selfish reasons--I am working on a praxis and have thousands of > cross streets I need to geocode. > > Aren > > > On Tue, Nov 29, 2011 at 12:03 PM, Stephen Woodbridge < > wood...@swoodbridge.com> wrote: > >> On 11/29/2011 12:42 PM, Stephen Frost wrote: >> >>> * Stephen Woodbridge (wood...@swoodbridge.com) wrote: >>> >>>> I currently have some lists of names that are converted to optimized >>>> pcre regular expressions. I uses these to help separate the street >>>> from the city name. The lists are only used to create header files >>>> that contain the regular expressions that get compiled into the >>>> code. The idea being that these names are reasonably static for a >>>> given data set. >>>> >>> >>> Ah, ok, I see. When converting this to a PG function, I'd probably want >>> to go ahead and pull those lists from the TIGER data set and compile the >>> regexps on PG backend startup instead. Does it handle misspelled names >>> or do any kind of "sounds like" searching on the city names? I'm >>> guessing 'no', but figured I'd ask anyway.. >>> >> >> The lists that I have generated are pulled from a number of sources, like >> the actual tiger data, the fips 4-2 placenames, I also have some common >> abbreviations, and misspellings, but it is not doing any sounds like >> searching. I think that I broke the regular expressions into separate state >> specific regular expressions because putting them all into a sine >> expression exceeded some limit in pcre. >> >> The regex expressions are created in perl and are highly optimized. You >> probably can not read the regex's and make much sense out of them, but they >> are extremely efficient to evaluate. >> >> Also you can take just that directory from PAGC and build it and it >> should create a command line executable that you can test with and run it >> in the debugger and valgrind, etc. Something like: >> >> cd parseaddress >> ./configure >> make >> ./parseaddress 101 W MLK AVE NORTH CHELMSFORD MA 01863 >> >> >> -Steve >> ______________________________**_________________ >> postgis-users mailing list >> postgis-users@postgis.**refractions.net<postgis-users@postgis.refractions.net> >> http://postgis.refractions.**net/mailman/listinfo/postgis-**users<http://postgis.refractions.net/mailman/listinfo/postgis-users> >> > >
_______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users