[postgis-tickets] r15986 - Update docs to reflect zcta5 fix and also upgrade to tiger 2017 load
Regina Obe
lr at pcorp.us
Sun Oct 15 10:51:08 PDT 2017
Author: robe
Date: 2017-10-15 10:51:08 -0700 (Sun, 15 Oct 2017)
New Revision: 15986
Modified:
trunk/doc/extras_tigergeocoder.xml
trunk/doc/installation.xml
trunk/doc/xsl/postgis_aggs_mm.xml.xsl
Log:
Update docs to reflect zcta5 fix and also upgrade to tiger 2017 load
References #3815 for trunk PostGIS 2.5.0
Modified: trunk/doc/extras_tigergeocoder.xml
===================================================================
--- trunk/doc/extras_tigergeocoder.xml 2017-10-15 16:33:59 UTC (rev 15985)
+++ trunk/doc/extras_tigergeocoder.xml 2017-10-15 17:51:08 UTC (rev 15986)
@@ -375,6 +375,7 @@
</refsection>
</refentry>
+
<refentry id="Geocode_Intersection">
<refnamediv>
<refname>Geocode_Intersection</refname>
@@ -839,8 +840,11 @@
<para><varname>loader_lookuptables</varname> each record defines a kind of table (state, county), whether to process records in it and how to load them in. Defines the steps to import data, stage data, add, removes columns, indexes, and constraints for each. Each table is prefixed with the state and inherits from a table in the tiger schema. e.g. creates <varname>tiger_data.ma_faces</varname> which inherits from <varname>tiger.faces</varname></para>
</listitem>
</orderedlist>
+ <para>Changed: 2.4.1 zip code 5 tabulation area (zcta5) load step was fixed and when enabled, zcta5 data is loaded as a single table called zcta5_all as part of the nation script load.</para>
<para>Availability: 2.1.0 </para>
- <note><para>If you were running <varname>tiger_2010</varname> version and you want to reload as state with <varname>tiger_2011</varname>, you'll need to for the very first load generate and run drop statements <xref linkend="Drop_Nation_Tables_Generate_Script" /> before you run this script.</para></note>
+ <note><para>If you want zip code 5 tabulation area (zcta5) to be included in your nation script load, do the following:</para> <programlisting>UPDATE tiger.loader_lookuptables SET load = true WHERE table_name = 'zcta510';</programlisting></note>
+ <note><para>If you were running <varname>tiger_2010</varname> version and you want to reload as state with newer tiger data, you'll need to for the very first load generate and run drop statements <xref linkend="Drop_Nation_Tables_Generate_Script" /> before you run this script.</para></note>
+
</refsection>
Modified: trunk/doc/installation.xml
===================================================================
--- trunk/doc/installation.xml 2017-10-15 16:33:59 UTC (rev 15985)
+++ trunk/doc/installation.xml 2017-10-15 17:51:08 UTC (rev 15986)
@@ -1547,9 +1547,9 @@
<listitem><para>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 <varname>fuzzystrmatch</varname> extension already installed, you don't need to do the second step either.</para>
<para><programlisting>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;</programlisting></para>
+CREATE EXTENSION address_standardizer;</programlisting></para>
<para>If you already have postgis_tiger_geocoder extension installed, and just want to update to the latest run:</para>
<programlisting>ALTER EXTENSION postgis UPDATE;
@@ -1576,6 +1576,13 @@
<para>If you don't edit this <varname>loader_platform</varname> table, it will just contain common case locations of items and you'll have to edit the generated script after the script is generated.</para>
</listitem>
+ <listitem><para>As of PostGIS 2.4.1 the Zip code-5 digit tabulation area <varname>zcta5</varname> load step was revised to load current zcta5 data and is part of the <xref linkend="Loader_Generate_Nation_Script" /> when enabled.
+It is turned off by default because it takes quite a bit of time to load (20 to 60 minutes), takes up quite a bit of disk space, and is not used that often.</para>
+<para>To enable it, do the following:</para>
+<programlisting>UPDATE tiger.loader_lookuptables SET load = true WHERE table_name = 'zcta510';</programlisting>
+<para>
+If present the <xref linkend="Geocode" /> function can use it if a boundary filter is added to limit to just zips in that boundary.
+The <xref linkend="Reverse_Geocode" /> function uses it if the returned address is missing a zip, which often happens with highway reverse geocoding.</para></listitem>
<listitem><para>Create a folder called <filename>gisdata</filename> 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 <varname>staging_fold</varname> in the <varname>tiger.loader_variables</varname> table.</para></listitem>
<listitem><para>Create a folder called temp in the <filename>gisdata</filename> folder or whereever you designated the <varname>staging_fold</varname> to be. This will be
Modified: trunk/doc/xsl/postgis_aggs_mm.xml.xsl
===================================================================
--- trunk/doc/xsl/postgis_aggs_mm.xml.xsl 2017-10-15 16:33:59 UTC (rev 15985)
+++ trunk/doc/xsl/postgis_aggs_mm.xml.xsl 2017-10-15 17:51:08 UTC (rev 15986)
@@ -522,6 +522,7 @@
<xsl:if test="//para[contains(text(),'Enhanced: 2.4')]">
<para>Functions enhanced in PostGIS 2.4</para>
<para>All aggregates now marked as parallel safe which should allow them to be used in plans that can employ parallelism.</para>
+ <para>PostGIS 2.4.1 postgis_tiger_geocoder set to load Tiger 2017 data. Can optionally load zip code 5-digit tabulation (zcta) as part of the <xref linkend="Loader_Generate_Nation_Script" />.</para>
<itemizedlist>
<!-- Pull out the purpose section for each ref entry and strip whitespace and put in a variable to be tagged unto each function comment -->
<xsl:for-each select='//refentry'>
More information about the postgis-tickets
mailing list