From: Regina Obe Date: Fri, 18 Jul 2014 06:56:12 +0000 (+0000) Subject: update install instructions to reflect code is now part of repo X-Git-Tag: 2.2.0rc1~965 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=490090404dd1b34c5903769d68b838b6a9848717;p=postgis update install instructions to reflect code is now part of repo git-svn-id: http://svn.osgeo.org/postgis/trunk@12795 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/installation.xml b/doc/installation.xml index 3a306712e..a7cd6e5d2 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1202,6 +1202,33 @@ Run tests: 90 You can later run uninstall_legacy.sql to get rid of the deprecated functions after you are done with restoring and cleanup. + Installing and Using ddress standardizer + The address_standardizer extension used to be a separate package that required separate download. From PostGIS 2.2 on, it is now bundled in. + For more information about the address_standardize, what it does, and how to configure it for your needs, refer to . + This standardizer can be use in conjunction with the PostGIS packaged tiger geocoder extension as a replacement for the discussed. + To use as replacement refer to . + You can also use it as a building block for your own geocoder. + + The address standardizer relies on PCRE which is usually already installed on most Nix systems, +but you can download the latest at: http://www.pcre.org. It also requires Perl with the Regexp::Assemble installed + 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. + Installing Regex::Assemble + cpan Regexp::Assemble + or if you are on Ubuntu / Debian you might need to do + sudo perl -MCPAN -e "install Regexp::Assemble" + Compiling + cd postgis-&last_release_version;/extras/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; + + + + Installing, Upgrading Tiger Geocoder and loading data @@ -1250,30 +1277,6 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, - Installing and 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. - 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. It also requires Perl with the Regexp::Assemble installed - 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. - Installing Regex::Assemble - cpan Regexp::Assemble - or if you are on Ubuntu / Debian you might need to do - sudo perl -MCPAN -e "install Regexp::Assemble" - 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. - - Tiger Geocoder Enabling your PostGIS database: Not Using Extensions @@ -1308,6 +1311,12 @@ pretty_address + Using Address Standardizer Extension with Tiger geocoder + 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. To use this new address_standardizer, you compile the extension as described in and install as an extension in your database. + + Once you install this extension in the same database as you have installed postgis_tiger_geocoder, then the can be used instead of . This extension is tiger agnostic, so can be used with other data sources such as international addresses. The tiger geocoder extension does come packaged with its own custom versions of ( tiger.pagc_rules) , (tiger.pagc_gaz), and (tiger.pagc_lex). These you can add and update to improve your standardizing experience for your own needs. + Loading Tiger Data The instructions for loading data are available in a more detailed form in the extras/tiger_geocoder/tiger_2011/README. This just includes the general steps.