#2367 briefly document pagc in docs and where to get. will flesh out later, but...

git-svn-id: http://svn.osgeo.org/postgis/trunk@11649 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml
index 51f1c832ade3541513272f3323f152e46e0e0720..86d51de61987d9a3236c1a86e96f57098e9df54b 100644 (file)
--- a/doc/extras_tigergeocoder.xml
+++ b/doc/extras_tigergeocoder.xml
@@ -12,7 +12,7 @@
                        <para>All the geocode functions only reference the base tables, so there is no requirement that the data schema be called <varname>tiger_data</varname> or that data can't be further partitioned into other schemas -- e.g a different schema
                        for each state, as long as all the tables inherit from the tables in the <varname>tiger</varname> schema.</para>
                        
-                       <para>
+               
                          <note><para>
 If you are using tiger geocoder (tiger_2010),
 you can upgrade the scripts using the accompanying upgrade_geocoder.bat
@@ -21,7 +21,9 @@ until release.  If you have data from tiger_2010 and want replace with tiger_201
                          </para></note>
                          
                          <note><para>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 <xref linkend="install_tiger_geocoder_extension" /> for details.</para></note>
-                       </para>
+                         
+                         <para>Also new in PostGIS 2.1.0 is integration with pagc address standardizer C library which source can be downloaded from <ulink url="http://pagc.svn.sourceforge.net/viewvc/pagc/branches/sew-refactor/postgresql">PAGC PostgreSQL address standardizer extension</ulink> and after install and install of the libraray in your PostGIS database, you can use the <xref linkend="pagc_normalize_address" /> function as a drop in replacement for in-built <xref linkend="normalize_address" />.</para> 
+               
 
 
                        <para>Design:</para>

diff --git a/doc/installation.xml b/doc/installation.xml
index 975678d20e8ddb7a47f824b389c914a1e84a42e7..5e2185e862040a8e17ee7fedf8d424e3534e70ef 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -23,7 +23,7 @@ psql -d yourdatabase -c "CREATE EXTENSION postgis_tiger_geocoder;"</programlisti
        
        <para>Please refer to <xref linkend="make_install_postgis_extensions" /> for more details about querying installed/available extensions and upgrading extensions, or switching from a non-extension install to an extension install.</para>
        
-       <para>For those who decided for some reason not to compile with raster support, or just are old-fashioned, here are longer more painful instructions for you:</para>
+       <para>For those running PostgreSQL 9.0 or who decided for some reason not to compile with raster support, or just are old-fashioned, here are longer more painful instructions for you:</para>
        <para>All the .sql files once installed will be installed in share/contrib/postgis-&last_minor_version; folder
                of your PostgreSQL install</para>
 
@@ -1189,8 +1189,7 @@ Run tests: 90</programlisting>
   <sect1 id="loading_extras_tiger_geocoder">
        <title>Installing, Upgrading Tiger Geocoder and loading data</title>
        
-       <para>The Tiger geocoder does not get installed / upgraded with the core PostGIS scripts because it is only of regional use.  In fact nothing located
-       in the extras folder is installed by default with the regular PostGIS install / upgrade.  Extras like Tiger geocoder may also not be packaged in your PostGIS distribution, but will always be available in the postgis-&last_release_version;.tar.gz file. The instructions provided here are also available in the <filename>extras/tiger_geocoder/tiger_2011/README</filename> </para>
+       <para>Extras like Tiger geocoder may not be packaged in your PostGIS distribution, but will always be available in the postgis-&last_release_version;.tar.gz file. The instructions provided here are also available in the <filename>extras/tiger_geocoder/tiger_2011/README</filename> </para>
        <para>If you are on Windows and you don't have tar installed, you can use <ulink url="http://www.7-zip.org/">http://www.7-zip.org/</ulink> to unzip the PostGIS tarball.</para>
        <sect2 id="install_tiger_geocoder_extension">
                <title>Tiger Geocoder Enabling your PostGIS database: Using Extension</title>   
@@ -1234,6 +1233,15 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,
                                </listitem>
                        </orderedlist>
                </sect3>
+               
+               <sect3 id="installing_pagc_address_standardizer"><title>Using PAGC address standardizer</title>
+                       <para>One of the many complaints of folks is the address normalizer function <xref linkend="normalize_address" /> 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 <ulink url="http://pagc.svn.sourceforge.net/viewvc/pagc/branches/sew-refactor/postgresql">PAGC PostgreSQL Address Standardizer</ulink>.  To use this new normalizer, you compile the pagc extension and install as an extension in your database with:</para>
+                       <programlisting>CREATE EXTENSION address_standardizer;</programlisting>
+                       
+                       <para>Once you install this extension in the same database as you have installed <code>postgis_tiger_geocoder</code>, then the <xref linkend="pagc_normalize_address" /> can be used instead of <xref linkend="normalize_address" />. The other nice thing about this extension is that its tiger agnostic, so can be used with other data sources such as international addresses.</para>
+
+               </sect3>
        </sect2>
        <sect2 id="install_tiger_geocoder">
                <title>Tiger Geocoder Enabling your PostGIS database: Not Using Extensions</title>