From: Regina Obe Date: Wed, 30 Sep 2015 04:33:44 +0000 (+0000) Subject: try to fix illegal abstract (with note (instead of para)) and listltiem with no para X-Git-Tag: 2.2.0~43 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=de9dc4f402e616504d4d1eaf550e8f5b31638e83;p=postgis try to fix illegal abstract (with note (instead of para)) and listltiem with no para git-svn-id: http://svn.osgeo.org/postgis/trunk@14149 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml index 282fc6364..d2e8029e8 100644 --- a/doc/extras_tigergeocoder.xml +++ b/doc/extras_tigergeocoder.xml @@ -12,10 +12,11 @@ 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 instructions on how enable the extension in your database and also to load data using it, refer to Refer to . - + If you are using tiger geocoder (tiger_2010), you can upgrade the scripts using the accompanying upgrade_geocoder.bat / .sh scripts in extras/tiger. One major change between tiger_2010 and tiger_2011+ is that the county and county and state tables are no longer broken out by state. If you have data from tiger_2010 and want replace with tiger_2015 refer to @@ -24,6 +25,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. @@ -37,7 +39,7 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat It should be robust enough to function properly despite formatting and spelling errors. It should be extensible enough to be used with future data updates, or alternate data sources with a minimum of coding changes. - The tiger schema must be added to the database search path for the functions to work properly. + The tiger schema must be added to the database search path for the functions to work properly. diff --git a/doc/installation.xml b/doc/installation.xml index e596420b7..9b3880aab 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1564,10 +1564,10 @@ 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. + 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');