minor updates to PAGC

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

diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml
index 181f121c5c0860e1e78cbc0513477c7feb55f694..3975cf2048665789dde0f145bfc1ff85474bd35c 100644 (file)
--- a/doc/extras_tigergeocoder.xml
+++ b/doc/extras_tigergeocoder.xml
@@ -1061,11 +1061,11 @@ FROM pagc_normalize_address('9000 E ROO ST STE 999, Springfield, CO') AS addy;
         
  address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal  |  location   | stateabbrev | zip | parsed
 ---------+--------------+------------+------------------+---------------+-----------+-------------+-------------+-----+--------
-    9000 | E            | ROO        | St               |               | SUITE 999 | SPRINGFIELD | CO          |     | t</programlisting>
+    9000 | E            | ROO        | ST               |               | SUITE 999 | SPRINGFIELD | CO          |     | t</programlisting>
     
                <para>Batch call.  There are currently speed issues with the way postgis_tiger_geocoder wraps the address_standardizer.  These will hopefully
 be resolved in later editions.  To work around them, if you need speed for batch geocoding to call generate a normaddy  in batch mode, you are encouraged
-to directly call the address_standardizer standardize_address function as shown below which is similar exercise to what we did in <xref linkend="Normalize_Address" />.</para>
+to directly call the address_standardizer standardize_address function as shown below which is similar exercise to what we did in <xref linkend="Normalize_Address" /> that uses data created in <xref linkend="Geocode" />.</para>
     
     <programlisting>WITH g AS (SELECT address, ROW((sa).house_num, (sa).predir, (sa).name
   , (sa).suftype, (sa).sufdir, (sa).unit , (sa).city, (sa).state, (sa).postcode, true)::norm_addy As na
@@ -1078,12 +1078,12 @@ SELECT address As orig, (g.na).streetname, (g.na).streettypeabbrev
  
  orig                                                |  streetname   | streettypeabbrev
 -----------------------------------------------------+---------------+------------------
- 529 Main Street, Boston MA, 02129                   | MAIN          | St
- 77 Massachusetts Avenue, Cambridge, MA 02139        | MASSACHUSETTS | Ave
+ 529 Main Street, Boston MA, 02129                   | MAIN          | ST
+ 77 Massachusetts Avenue, Cambridge, MA 02139        | MASSACHUSETTS | AVE
  25 Wizard of Oz, Walaford, KS 99912323              | WIZARD OF     |
- 26 Capen Street, Medford, MA                        | CAPEN         | St
- 124 Mount Auburn St, Cambridge, Massachusetts 02138 | MOUNT AUBURN  | St
- 950 Main Street, Worcester, MA 01610                | MAIN          | St</programlisting>
+ 26 Capen Street, Medford, MA                        | CAPEN         | ST
+ 124 Mount Auburn St, Cambridge, Massachusetts 02138 | MOUNT AUBURN  | ST
+ 950 Main Street, Worcester, MA 01610                | MAIN          | ST</programlisting>
                </refsection>
          <!-- Optionally add a "See Also" section -->
          <refsection>

diff --git a/doc/installation.xml b/doc/installation.xml
index 5b39751619b4e6ca84fe941b3eb4b5403f47d7fc..c828b042ef169695589b044a260c50f47e254a81 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1236,7 +1236,7 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,
                
                <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://sourceforge.net/p/pagc/code/360/tree/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>
+                       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://sourceforge.net/p/pagc/code/360/tree/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.</para>
                        <para>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: <ulink url="http://www.pcre.org">http://www.pcre.org</ulink> </para>
                        <para>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 <code>CREATE EXTENSION</code> step.</para>