From: | Webb Sprague <webb(dot)sprague(at)gmail(dot)com> |
---|---|
To: | |
Cc: | Postgresql PDX_Users <pdxpug(at)postgresql(dot)org> |
Subject: | Re: SQL Work Needed at the City of Wilsonville |
Date: | 2011-08-02 15:05:12 |
Message-ID: | CAHwPRku46a_=pVHnxEa+ixSThWmBPigugHjOVK89__awGe1s4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
On Tue, Aug 2, 2011 at 7:52 AM, Shawn Helm <helm(dot)shawn(at)gmail(dot)com> wrote:
> Here is a better link on postgis address normalization with actual code:
> http://svn.osgeo.org/postgis/trunk/extras/tiger_geocoder/tiger_2010/normalize/
If the data was loaded into a postgres db with postgis + geocoder
installed, you would have not just the address normalization routines
there to use almost seamlessly, but also lots and lots of other useful
things for string manipulation built into Postgres. Postgres and
Postgis install easily on a windows machine, though (obviously ;)) a
Unix variant is far superior.
(I am being flip about Unix, but big data pipelines are much easier to
script in a Unix environment, though trickier to get used to the
command line. Sorry for any preaching to the converted....)
From | Date | Subject | |
---|---|---|---|
Next Message | daniel stark | 2011-08-02 18:15:04 | Re: SQL Work Needed at the City of Wilsonville |
Previous Message | Shawn Helm | 2011-08-02 14:52:47 | Re: SQL Work Needed at the City of Wilsonville |