From: Regina Obe Date: Fri, 19 Jul 2013 04:04:10 +0000 (+0000) Subject: update pagc install instructions X-Git-Tag: 2.2.0rc1~1439 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1fc0f226d9993992687485b1c871a8bb60eae921;p=postgis update pagc install instructions git-svn-id: http://svn.osgeo.org/postgis/trunk@11699 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml index 60b4fc937..330718990 100644 --- a/doc/extras_tigergeocoder.xml +++ b/doc/extras_tigergeocoder.xml @@ -22,7 +22,7 @@ until release. If you have data from tiger_2010 and want replace with tiger_201 New in PostGIS 2.1.0 release is ability to install tiger geocoder with PostgreSQL extension model if you are running PostgreSQL 9.1+. Refer to for details. - Also new in PostGIS 2.1.0 is integration with pagc address standardizer C library which source can be downloaded from PAGC PostgreSQL address standardizer extension and after install and install of the libraray in your PostGIS database, you can use the function as a drop in replacement for in-built . + Also new in PostGIS 2.1.0 is integration with pagc address standardizer PostgreSQL extension which source can be downloaded from PAGC PostgreSQL address standardizer extension and after install and install of the library in your PostGIS database, you can use the function as a drop in replacement for in-built . diff --git a/doc/installation.xml b/doc/installation.xml index e6657cffe..4a3d404b5 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1236,7 +1236,19 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, Using PAGC address standardizer One of the many complaints of folks is the address normalizer function function that normalizes an address for prepping before geocoding. The normalizer is far from perfect and trying to patch its imperfectness takes a vast amount of resources. As such we have integrated with another - project that has a much better address standardizer engine. This is currently a separate project, which is a subproject of PAGC. The source code for this PostgreSQL standardizer extension can be downloaded from PAGC PostgreSQL Address Standardizer. To use this new normalizer, you compile the pagc extension and install as an extension in your database with: + project that has a much better address standardizer engine. This is currently a separate project, which is a subproject of PAGC. The source code for this PostgreSQL standardizer extension can be downloaded from PAGC PostgreSQL Address Standardizer. To use this new normalizer, you compile the pagc extension and install as an extension in your database with: + The PAGC project and standardizer portion in particular, relies on PCRE which is usually already installed on most Nix systems, +but you can download the latest at: http://www.pcre.org + For Windows users, the PostGIS 2.1+ bundle will come packaged with the address_standardizer already so no need to compile and can move straight to CREATE EXTENSION step. + Compiling + svn co svn://svn.code.sf.net/p/pagc/code/branches/sew-refactor/postgresql address_standardizer +cd address_standardizer +make +#if you have in non-standard location pcre try +# make SHLIB_LINK="-L$/path/pcre/lib -lpostgres -lpgport -lpcre" CPPFLAGS="-I. -I$/path/pcre/include" +make install + + Once you have installed, you can connect to your database and run the SQL: CREATE EXTENSION address_standardizer; Once you install this extension in the same database as you have installed postgis_tiger_geocoder, then the can be used instead of . The other nice thing about this extension is that its tiger agnostic, so can be used with other data sources such as international addresses.