From: Regina Obe Date: Wed, 30 Sep 2015 03:19:37 +0000 (+0000) Subject: update tiger instructions to be comprehensive (next step will be to delete them from... X-Git-Tag: 2.2.0~44 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2987940a76e5fa2bfe31e7d6ae6200ce6dd75e90;p=postgis update tiger instructions to be comprehensive (next step will be to delete them from README os have only one source to edit). Also add a note about using GUC for raster settings (instead of less cross-platform environment approach) git-svn-id: http://svn.osgeo.org/postgis/trunk@14148 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml index 72304d10b..282fc6364 100644 --- a/doc/extras_tigergeocoder.xml +++ b/doc/extras_tigergeocoder.xml @@ -10,7 +10,9 @@ Another schema called tiger_data is also created which houses all the census data for each state that the loader downloads from Census site and loads into the database. In the current model, each set of state tables is prefixed with the state code e.g ma_addr, ma_edges etc with constraints to enforce only that state data. Each of these tables inherits from the tables addr, faces, edges, etc located in the tiger schema. All the geocode functions only reference the base tables, so there is no requirement that the data schema be called tiger_data 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 tiger schema. + for each state, as long as all the tables inherit from the tables in the tiger schema. + + For instructions on how enable the extension in your database and also to load data using it, refer to Refer to . @@ -22,7 +24,7 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat New in PostGIS 2.2.0 release is support for Tiger 2015 data and inclusion of Address Standardizer as part of PostGIS. 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. - + The function as a drop in replacement for in-built . Refer to for compile and installation instructions. diff --git a/doc/installation.xml b/doc/installation.xml index 155e0a650..e596420b7 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -56,8 +56,8 @@ psql -d yourdatabase -f sfcgal_comments.sql steps. - As of PostGIS 2.1.3, out-of-db rasters and all raster drivers are disabled by default. In order to re-enable these, you need to set the following environment variables: - POSTGIS_GDAL_ENABLED_DRIVERS and POSTGIS_ENABLE_OUTDB_RASTERS in the server environment. + As of PostGIS 2.1.3, out-of-db rasters and all raster drivers are disabled by default. In order to re-enable these, you need to set the following environment variables + POSTGIS_GDAL_ENABLED_DRIVERS and POSTGIS_ENABLE_OUTDB_RASTERS in the server environment. For PostGIS 2.2, you can use the more cross-platform approach of setting the corresponding . If you want to enable offline raster: POSTGIS_ENABLE_OUTDB_RASTERS=1 @@ -1535,7 +1535,15 @@ but you can download the latest at: http://www. Connect to your database via psql or pgAdmin or some other tool and run the following SQL commands. Note that if you are installing in a database that already has postgis, you don't need to do the first step. If you have fuzzystrmatch extension already installed, you don't need to do the second step either. CREATE EXTENSION postgis; CREATE EXTENSION fuzzystrmatch; -CREATE EXTENSION postgis_tiger_geocoder; +--this one is optional if you want to use the rules based standardizer (pagc_normalize_address) +CREATE EXTENSION address_standardizer; +CREATE EXTENSION postgis_tiger_geocoder; + +If you already have postgis_tiger_geocoder extension installed, and just want to update to the latest run: +ALTER EXTENSION postgis UPDATE; +ALTER EXTENSION postgis_tiger_geocoder UPDATE; +If you made custom entries or changes to tiger.loader_platform and tiger.loader_variables you may need to update these. + To confirm your install is working correctly, run this sql in your database: SELECT na.address, na.streetname,na.streettypeabbrev, na.zip FROM normalize_address('1 Devonshire Place, Boston, MA 02109') AS na; @@ -1556,11 +1564,16 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, If you don't edit this loader_platform table, it will just contain common case locations of items and you'll have to edit the generated script after the script is generated. + Create a folder called gisdata on root of server or your local pc if you have a fast network connection to the server. This folder is +where the tiger files will be downloaded to and processed. If you are not happy with having the folder on the root of the server, or simply want to change to a different folder for staging, then edit the field staging_fold in the tiger.loader_variables table. + Create a folder called temp in the gisdata folder or whereever you designated the staging_fold to be. This will be +the folder where the loader extracts the downloaded tiger data. Then run the and SQL functions make sure to use the name of your custom profile and copy the scripts to a .sh or .bat file. So for example to do the nation load and one state using our new profile we would: SELECT Loader_Generate_Nation_Script('debbie'); SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie'); - Run the generated scripts. + + Run the generated commandline scripts. After you are done loading all data or at a stopping point, it's a good idea to analyze all the tiger tables to update the stats (include inherited stats) SELECT install_missing_indexes(); vacuum analyze verbose tiger.addr;