#strip BEGIN/COMMIT since these are not allowed in extensions
#strip CREATE SCHEMA since we force extension
# to create schema by setting schema to tiger_geocoder in control
-sql_bits/tiger_geocoder_minor.sql.in: ../../extras/tiger_geocoder/tiger_2011/utility/set_search_path.sql \
- ../../extras/tiger_geocoder/tiger_2011/tiger_loader_2014.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/utmzone.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/cull_null.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/nullable_levenshtein.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/levenshtein_ignore_case.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/end_soundex.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/count_words.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/state_extract.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/get_last_words.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_countysub_exact.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_countysub_fuzzy.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_place_exact.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_place_fuzzy.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/normalize_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/pprint_addy.sql \
- ../../extras/tiger_geocoder/tiger_2011/pagc_normalize/pagc_tables.sql \
- ../../extras/tiger_geocoder/tiger_2011/pagc_normalize/pagc_normalize_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/other_helper_functions.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/rate_attributes.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/includes_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/interpolate_from_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode_location.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode_intersection.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/reverse_geocode.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/census_tracts_functions.sql
+sql_bits/tiger_geocoder_minor.sql.in: ../../extras/tiger_geocoder/utility/set_search_path.sql \
+ ../../extras/tiger_geocoder/tiger_loader_2014.sql \
+ ../../extras/tiger_geocoder/utility/utmzone.sql \
+ ../../extras/tiger_geocoder/utility/cull_null.sql \
+ ../../extras/tiger_geocoder/utility/nullable_levenshtein.sql \
+ ../../extras/tiger_geocoder/utility/levenshtein_ignore_case.sql \
+ ../../extras/tiger_geocoder/normalize/end_soundex.sql \
+ ../../extras/tiger_geocoder/normalize/count_words.sql \
+ ../../extras/tiger_geocoder/normalize/state_extract.sql \
+ ../../extras/tiger_geocoder/normalize/get_last_words.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_countysub_exact.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_countysub_fuzzy.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_place_exact.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_place_fuzzy.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract.sql \
+ ../../extras/tiger_geocoder/normalize/normalize_address.sql \
+ ../../extras/tiger_geocoder/normalize/pprint_addy.sql \
+ ../../extras/tiger_geocoder/pagc_normalize/pagc_tables.sql \
+ ../../extras/tiger_geocoder/pagc_normalize/pagc_normalize_address.sql \
+ ../../extras/tiger_geocoder/geocode/other_helper_functions.sql \
+ ../../extras/tiger_geocoder/geocode/rate_attributes.sql \
+ ../../extras/tiger_geocoder/geocode/includes_address.sql \
+ ../../extras/tiger_geocoder/geocode/interpolate_from_address.sql \
+ ../../extras/tiger_geocoder/geocode/geocode_address.sql \
+ ../../extras/tiger_geocoder/geocode/geocode_location.sql \
+ ../../extras/tiger_geocoder/geocode/geocode_intersection.sql \
+ ../../extras/tiger_geocoder/geocode/geocode.sql \
+ ../../extras/tiger_geocoder/geocode/reverse_geocode.sql \
+ ../../extras/tiger_geocoder/geocode/census_tracts_functions.sql
cat $^ > $@
sql_bits/tiger_geocoder.sql.in: sql_bits/norm_addy_create.sql.in \
- ../../extras/tiger_geocoder/tiger_2011/utility/set_search_path.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode_settings.sql \
- ../../extras/tiger_geocoder/tiger_2011/tables/lookup_tables_2011.sql \
- ../../extras/tiger_geocoder/tiger_2011/tiger_loader_2014.sql \
- ../../extras/tiger_geocoder/tiger_2011/census_loader.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/set_search_path.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/utmzone.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/cull_null.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/nullable_levenshtein.sql \
- ../../extras/tiger_geocoder/tiger_2011/utility/levenshtein_ignore_case.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/end_soundex.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/count_words.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/state_extract.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/get_last_words.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_countysub_exact.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_countysub_fuzzy.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_place_exact.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract_place_fuzzy.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/location_extract.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/normalize_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/normalize/pprint_addy.sql \
- ../../extras/tiger_geocoder/tiger_2011/pagc_normalize/pagc_tables.sql \
- ../../extras/tiger_geocoder/tiger_2011/pagc_normalize/pagc_normalize_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/other_helper_functions.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/rate_attributes.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/includes_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/interpolate_from_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode_address.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode_location.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode_intersection.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/geocode.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/reverse_geocode.sql \
- ../../extras/tiger_geocoder/tiger_2011/geocode/census_tracts_functions.sql \
- ../../extras/tiger_geocoder/tiger_2011/topology/tiger_topology_loader.sql \
+ ../../extras/tiger_geocoder/utility/set_search_path.sql \
+ ../../extras/tiger_geocoder/geocode_settings.sql \
+ ../../extras/tiger_geocoder/tables/lookup_tables_2011.sql \
+ ../../extras/tiger_geocoder/tiger_loader_2014.sql \
+ ../../extras/tiger_geocoder/census_loader.sql \
+ ../../extras/tiger_geocoder/utility/set_search_path.sql \
+ ../../extras/tiger_geocoder/utility/utmzone.sql \
+ ../../extras/tiger_geocoder/utility/cull_null.sql \
+ ../../extras/tiger_geocoder/utility/nullable_levenshtein.sql \
+ ../../extras/tiger_geocoder/utility/levenshtein_ignore_case.sql \
+ ../../extras/tiger_geocoder/normalize/end_soundex.sql \
+ ../../extras/tiger_geocoder/normalize/count_words.sql \
+ ../../extras/tiger_geocoder/normalize/state_extract.sql \
+ ../../extras/tiger_geocoder/normalize/get_last_words.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_countysub_exact.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_countysub_fuzzy.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_place_exact.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract_place_fuzzy.sql \
+ ../../extras/tiger_geocoder/normalize/location_extract.sql \
+ ../../extras/tiger_geocoder/normalize/normalize_address.sql \
+ ../../extras/tiger_geocoder/normalize/pprint_addy.sql \
+ ../../extras/tiger_geocoder/pagc_normalize/pagc_tables.sql \
+ ../../extras/tiger_geocoder/pagc_normalize/pagc_normalize_address.sql \
+ ../../extras/tiger_geocoder/geocode/other_helper_functions.sql \
+ ../../extras/tiger_geocoder/geocode/rate_attributes.sql \
+ ../../extras/tiger_geocoder/geocode/includes_address.sql \
+ ../../extras/tiger_geocoder/geocode/interpolate_from_address.sql \
+ ../../extras/tiger_geocoder/geocode/geocode_address.sql \
+ ../../extras/tiger_geocoder/geocode/geocode_location.sql \
+ ../../extras/tiger_geocoder/geocode/geocode_intersection.sql \
+ ../../extras/tiger_geocoder/geocode/geocode.sql \
+ ../../extras/tiger_geocoder/geocode/reverse_geocode.sql \
+ ../../extras/tiger_geocoder/geocode/census_tracts_functions.sql \
+ ../../extras/tiger_geocoder/topology/tiger_topology_loader.sql \
../postgis_extension_helper.sql \
sql_bits/add_search_path.sql \
../postgis_extension_helper_uninstall.sql
-TIGER Geocoder
- 2013/07/09
+Installing The Tiger Geocoder
- A plpgsql based geocoder written for TIGER census data.
+This is a customized version of Steve Frost's tiger geocoder revisions
+(http://www.snowman.net/git/tiger_geocoder/).
-Design:
+This version includes a loader that is portable between Linux and
+Windows but loads a full state of data at a time. The loader helper tables and
+functions are prefixed with loader and stored in the tiger schema. If
+you only want to load a county, revise the wget call that is generated
+for the state to just download the statewide and specific counties or
+just download them by hand. The loader will only process files that
+exist.
-There are two components to the geocoder, the address normalizer and the
-address geocoder. These two components are described separately.
+If you are on windows, you will need 7zip and wget. 7zip you can get
+from http://www.7-zip.org/ and wget you can get from
+http://gnuwin32.sourceforge.net/packages/wget.htm
-The goal of this project is to build a fully functional geocoder that can
-process an arbitrary address string and, using normalized TIGER census data,
-produce a point geometry reflecting the location of the given address.
+Tiger Geocoder is now part of the PostGIS documentation
+for further details about function use, refer to:
+http://www.postgis.net/docs/manual-dev/Extras.html#Tiger_Geocoder
-- The geocoder should be simple for anyone familiar with PostGIS to install
- and use.
-- 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.
+Steps to install and load (without using extensions)
-Installation:
+1. Create a PostGIS enabled db if you don't have one already
- Refer to the README in the respective year tiger folder for installation and example usage. The latest scripts as of this writing are for tiger_2012.
-
+2. From command line, cd into the tiger_geocoder_2011 folder
-Usage:
+3. Edit the tiger_loader.sql to the paths of your executables server etc.
- SELECT g.rating, g.geomout, (addy).* FROM geocode('address string') As g;
-
-e.g: SELECT g.rating,
- ST_X(geomout) As lon,
- ST_Y(geomout) As lat, (addy).* FROM geocode('1731 New Hampshire Avenue Northwest, Washington, DC 20010') As g;
+4. Edit the create_geocode.bat or create_geocode.sh and run
+
+5. Now add tiger schema to your database search path by doing
+something like:
+ALTER DATABASE geocoder SET search_path=public, tiger;
+
+Steps using extensions:
+1. Create a PostGIS enabled db make sure you installed postgis with:
+CREATE EXTENSION postgis;
+
+2) Next:
+CREATE EXTENSION postgis_tiger_geocoder;
+
+Loading up data:
+
+1. 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.
+
+2. Create a folder called temp in the gisdata folder. This will be
+the folder where we extract the downloaded tiger data.
+
+3. Run the following commands at psql or pgAdmin III query window to
+generate the script, replacing 'DC', 'RI' with list of states you want
+and save contents to a .bat or sh file in YOUR CURRENT DIRECTORY. This
+will generate CODE for each state and append it to the script.
+
+(IF YOU ARE AT A PSQL PROMPT, FIRST RUN "\a", "\t", AND "\o
+script.xxx". THIS WILL MAKE YOUR OUTPUT UNALIGNED AND REDIRECT IT TO
+script.xxx. WITHOUT "\a" and "\t", THE SCRIPT WILL HAVE EXTRA
+WHITESPACE AND POSSIBLY NON-SCRIPT CHARACTERS THAT CAUSE IT TO BREAK.)
+
+-- UNIX /LINUX USERS --
+-- Note even if you want just specific states you need to
+-- do this step since 2011 county, state tables are available only at national level
+SELECT loader_generate_nation_script('sh');
-Notes:
+-- After the nation load, generate a bash script suitable for Unix command lines
+-- for your desired states.
-- The assumed format for the address is the US Postal Service standard:
- () indicates a field required by the geocoder, [] indicates an optional field.
+SELECT loader_generate_script(ARRAY['DC','RI'], 'sh');
- (address) [dirPrefix] (streetName) [streetType] [dirSuffix]
- [internalAddress] [location] [state] [zipCode]
+ONCE YOU GENERATE THIS SCRIPT, EDIT IT TO ADD "set -e -u" AT THE TOP;
+THIS SETTING WILL MAKE IT STOP ON ERROR OR UNITIALIZED VARIABLE AND
+MAKE IT EASIER TO DEBUG ANY PROBLEMS.
+THEN RUN THE SCRIPT AT THE COMMAND LINE, REDIRECTING STANDARD OUTPUT AND
+STANDARD ERROR TO USEFUL FILES. YOU MAY WANT TO RUN "tail -f " TO SEE THE
+STANDARD ERROR AS IT GETS WRITTEN. FOR EXAMPLE:
+$ sh foo.sh 1>out 2>err; tail -f err
-Address Normalizer:
+-- WINDOWS USERS --
+--To generate a WINDOWS DOS script
+-- this will generate the script to download the national layers
+-- Note even if you want just specific states you need to
+-- do this step since 2011 county, state tables are available only at national level
+SELECT loader_generate_nation_script('windows');
-The goal of the address normalizer is to provide a robust function to break a
-given address string down into the components of an address. While the
-normalizer is built specifically for the normalized US TIGER Census data, it
-has been designed to be reasonably extensible to other data sets and localities.
+-- this you do after the nation load and for states you want
+SELECT loader_generate_script(ARRAY['DC','RI'], 'windows');
-Usage:
+If your script disappears without loading anything,
+most likely one of your path settings is wrong.
+To troubleshoot run the batch script by
+first opening up a commandline and executing the file.
- normalize_address('address string');
-
- e.g.: SELECT naddy.* FROM normalize_address('29645 7th Street SW Federal Way 98023') AS naddy;
-
- address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal | location | stateabbrev | zip | parsed
- ---------+-------------+-----------------------+------------------+---------------+----------+----------+-------------+-------+--------
- 29645 | | 7th Street SW Federal | Way | | | | | 98023 |
\ No newline at end of file
+That will keep the window open for you to see the error.
+
+-- Next run the script to install any missing indexes --
+SELECT install_missing_indexes();
+
+Alternatively if you want to see what indexes will be created before
+you create them run the below and manually run the steps generated:
+SELECT missing_indexes_generate_script();
+
+
+9. Copy and paste the generated script into a .bat or .sh file and put
+in gisdata folder you created and then run it, OR IF YOU REDIRECTED
+THE OUTPUT TO A FILE WITH "\o" MOVE THAT FILE TO GISDATA.
+
+10. Test out the geocoder run these queries
+
+-- To get the best rated answer --
+-- this is generally faster
+SELECT g.rating,
+ ST_X(geomout) As lon,
+ ST_Y(geomout) As lat, (addy).*
+FROM geocode('1731 New Hampshire Avenue Northwest, Washington, DC 20010', 1) As g;
+
+--To get multiple answers if there is more than 1
+SELECT g.rating,
+ ST_X(geomout) As lon,
+ ST_Y(geomout) As lat, (addy).*
+FROM geocode('1731 New Hampshire Avenue Northwest, Washington, DC 20010') As g;
+
+STEPS TO UPGRADE YOUR INSTALL:
+If you need to upgrade the geocoder/tiger loader from a pre-release
+2.0.0 install -- run the upgrade_geocoder.sh or upgrade_geocoder.bat
+script.
+
+CAUTION: The upgrade script will drop any table columns that have a
+norm_addy type for a column type. This is rare if ever done so you
+should be fine. We plan to fix this later. It will also drop any
+customizations you have made to the tiger_loader configuration tables.
+To prevent this, you can remark out the install loader part. This we
+plan to remedy in the future.
+
+It will also install any missing indexes that are deemed needed by
+queries.
+
+It will fail on some steps such as addition of new columns
+to lookup tables if they already exist in your intall.
+These errors can be safely ignored.
+++ /dev/null
-
-Installing The Tiger Geocoder
-
-This is a customized version of Steve Frost's tiger geocoder revisions
-(http://www.snowman.net/git/tiger_geocoder/).
-
-This version includes a loader that is portable between Linux and
-Windows but loads a full state of data at a time. The loader helper tables and
-functions are prefixed with loader and stored in the tiger schema. If
-you only want to load a county, revise the wget call that is generated
-for the state to just download the statewide and specific counties or
-just download them by hand. The loader will only process files that
-exist.
-
-If you are on windows, you will need 7zip and wget. 7zip you can get
-from http://www.7-zip.org/ and wget you can get from
-http://gnuwin32.sourceforge.net/packages/wget.htm
-
-Tiger Geocoder is now part of the PostGIS documentation
-for further details about function use, refer to:
-http://www.postgis.net/docs/manual-dev/Extras.html#Tiger_Geocoder
-
-Steps to install and load (without using extensions)
-
-1. Create a PostGIS enabled db if you don't have one already
-
-2. From command line, cd into the tiger_geocoder_2011 folder
-
-3. Edit the tiger_loader.sql to the paths of your executables server etc.
-
-4. Edit the create_geocode.bat or create_geocode.sh and run
-
-5. Now add tiger schema to your database search path by doing
-something like:
-ALTER DATABASE geocoder SET search_path=public, tiger;
-
-Steps using extensions:
-1. Create a PostGIS enabled db make sure you installed postgis with:
-CREATE EXTENSION postgis;
-
-2) Next:
-CREATE EXTENSION postgis_tiger_geocoder;
-
-Loading up data:
-
-1. 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.
-
-2. Create a folder called temp in the gisdata folder. This will be
-the folder where we extract the downloaded tiger data.
-
-3. Run the following commands at psql or pgAdmin III query window to
-generate the script, replacing 'DC', 'RI' with list of states you want
-and save contents to a .bat or sh file in YOUR CURRENT DIRECTORY. This
-will generate CODE for each state and append it to the script.
-
-(IF YOU ARE AT A PSQL PROMPT, FIRST RUN "\a", "\t", AND "\o
-script.xxx". THIS WILL MAKE YOUR OUTPUT UNALIGNED AND REDIRECT IT TO
-script.xxx. WITHOUT "\a" and "\t", THE SCRIPT WILL HAVE EXTRA
-WHITESPACE AND POSSIBLY NON-SCRIPT CHARACTERS THAT CAUSE IT TO BREAK.)
-
--- UNIX /LINUX USERS --
--- Note even if you want just specific states you need to
--- do this step since 2011 county, state tables are available only at national level
-SELECT loader_generate_nation_script('sh');
-
--- After the nation load, generate a bash script suitable for Unix command lines
--- for your desired states.
-
-SELECT loader_generate_script(ARRAY['DC','RI'], 'sh');
-
-
-ONCE YOU GENERATE THIS SCRIPT, EDIT IT TO ADD "set -e -u" AT THE TOP;
-THIS SETTING WILL MAKE IT STOP ON ERROR OR UNITIALIZED VARIABLE AND
-MAKE IT EASIER TO DEBUG ANY PROBLEMS.
-THEN RUN THE SCRIPT AT THE COMMAND LINE, REDIRECTING STANDARD OUTPUT AND
-STANDARD ERROR TO USEFUL FILES. YOU MAY WANT TO RUN "tail -f " TO SEE THE
-STANDARD ERROR AS IT GETS WRITTEN. FOR EXAMPLE:
-
-$ sh foo.sh 1>out 2>err; tail -f err
-
--- WINDOWS USERS --
---To generate a WINDOWS DOS script
--- this will generate the script to download the national layers
--- Note even if you want just specific states you need to
--- do this step since 2011 county, state tables are available only at national level
-SELECT loader_generate_nation_script('windows');
-
--- this you do after the nation load and for states you want
-SELECT loader_generate_script(ARRAY['DC','RI'], 'windows');
-
-If your script disappears without loading anything,
-most likely one of your path settings is wrong.
-To troubleshoot run the batch script by
-first opening up a commandline and executing the file.
-
-That will keep the window open for you to see the error.
-
--- Next run the script to install any missing indexes --
-SELECT install_missing_indexes();
-
-Alternatively if you want to see what indexes will be created before
-you create them run the below and manually run the steps generated:
-SELECT missing_indexes_generate_script();
-
-
-9. Copy and paste the generated script into a .bat or .sh file and put
-in gisdata folder you created and then run it, OR IF YOU REDIRECTED
-THE OUTPUT TO A FILE WITH "\o" MOVE THAT FILE TO GISDATA.
-
-10. Test out the geocoder run these queries
-
--- To get the best rated answer --
--- this is generally faster
-SELECT g.rating,
- ST_X(geomout) As lon,
- ST_Y(geomout) As lat, (addy).*
-FROM geocode('1731 New Hampshire Avenue Northwest, Washington, DC 20010', 1) As g;
-
---To get multiple answers if there is more than 1
-SELECT g.rating,
- ST_X(geomout) As lon,
- ST_Y(geomout) As lat, (addy).*
-FROM geocode('1731 New Hampshire Avenue Northwest, Washington, DC 20010') As g;
-
-STEPS TO UPGRADE YOUR INSTALL:
-If you need to upgrade the geocoder/tiger loader from a pre-release
-2.0.0 install -- run the upgrade_geocoder.sh or upgrade_geocoder.bat
-script.
-
-CAUTION: The upgrade script will drop any table columns that have a
-norm_addy type for a column type. This is rare if ever done so you
-should be fine. We plan to fix this later. It will also drop any
-customizations you have made to the tiger_loader configuration tables.
-To prevent this, you can remark out the install loader part. This we
-plan to remedy in the future.
-
-It will also install any missing indexes that are deemed needed by
-queries.
-
-It will fail on some steps such as addition of new columns
-to lookup tables if they already exist in your intall.
-These errors can be safely ignored.
projects / postgis / commitdiff