From: Regina Obe <lr@pcorp.us>
Date: Thu, 17 Jul 2014 04:12:32 +0000 (+0000)
Subject: finish listing all key user defined tables -- needs more work but a start
X-Git-Tag: 2.2.0rc1~972
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=898913b78b9e3811b3fdf4568dda627c219fc9fd;p=postgis

finish listing all key user defined tables -- needs more work but a start

git-svn-id: http://svn.osgeo.org/postgis/trunk@12788 b70326c6-7e19-0410-871a-916f4a2858ee
---

diff --git a/doc/extras_address_standardizer.xml b/doc/extras_address_standardizer.xml
index 622398800..a96ad75ac 100644
--- a/doc/extras_address_standardizer.xml
+++ b/doc/extras_address_standardizer.xml
@@ -142,7 +142,7 @@ into includes in the future for easier maintenance.</para></listitem>
         <title>Address Standardizer Tables</title>
         <refentry id="rulestab">
 					<refnamediv>
-					<refname>rules</refname>
+					<refname>rules table</refname>
 						<refpurpose>The rules table contains a set of rules that maps address input sequence tokens to standardized output sequence</refpurpose>
 					</refnamediv>
 					<refsection>
@@ -199,6 +199,92 @@ into includes in the future for easier maintenance.</para></listitem>
 								</varlistentry>
 						</variablelist>
 						
+					</refsection>
+				</refentry>
+				
+				<refentry id="lextab">
+					<refnamediv>
+					<refname>lex table</refname>
+						<refpurpose>A lex table is used to classify alphanumeric input and associate that input with (a) input tokens ( See Input Tokens) and (b) standardized representations.</refpurpose>
+					</refnamediv>
+					<refsection>
+						<title>Description</title>
+						<para>A lex (short for lexicon) table is used to classify alphanumeric input and associate that input with <ulink url="http://www.pagcgeo.org/docs/html/pagc-12.html#--i-tok--">(a) input tokens</ulink> and (b) standardized representations. Things you will find in these tables are <code>ONE</code> mapped to stdworkd: <code>1</code>.</para>
+						
+						<para>A lex has at least the following columns in the table. You may add</para>
+							<variablelist>
+								<varlistentry>
+										<term>id</term>
+										<listitem>
+											<para>Primary key of table</para>
+										</listitem>
+								</varlistentry>
+								<varlistentry><term>seq</term> 
+									<listitem>
+										<para>integer: definition number?</para>
+									</listitem>
+								</varlistentry>
+
+								<varlistentry><term>word</term> 
+									<listitem>
+										<para>text: the input word</para>
+									</listitem>
+								</varlistentry>
+								<varlistentry><term>stdword</term> 
+									<listitem>
+										<para>text: the standardized replacement word</para>
+									</listitem>
+								</varlistentry>
+								<varlistentry><term>token</term> 
+									<listitem>
+										<para>integer: the kind of word it is.  Only if it is used in this context will it be replaced. Refer to <ulink url="http://www.pagcgeo.org/docs/html/pagc-12.html#--i-tok--">PAGC Tokens</ulink>.</para>
+									</listitem>
+								</varlistentry>
+						</variablelist>
+					</refsection>
+				</refentry>
+				
+				<refentry id="gaztab">
+					<refnamediv>
+					<refname>gaz table</refname>
+						<refpurpose>A gaz table is used to standardize place names and associate that input with (a) input tokens ( See Input Tokens) and (b) standardized representations.</refpurpose>
+					</refnamediv>
+					<refsection>
+						<title>Description</title>
+						<para>A gaz (short for gazeteer) table is used to classify place names and associate that input with <ulink url="http://www.pagcgeo.org/docs/html/pagc-12.html#--i-tok--">(a) input tokens</ulink> and (b) standardized representations. For example if you are in US, you may load these with State Names and associated abbreviations.</para>
+						
+						<para>A gaz table has at least the following columns in the table. You may add more columns if you wish for your own purposes.</para>
+							<variablelist>
+								<varlistentry>
+										<term>id</term>
+										<listitem>
+											<para>Primary key of table</para>
+										</listitem>
+								</varlistentry>
+								<varlistentry><term>seq</term> 
+									<listitem>
+										<para>integer: definition number?</para>
+									</listitem>
+								</varlistentry>
+								<varlistentry><term>word</term> 
+									<listitem>
+										<para>text: the input word</para>
+									</listitem>
+								</varlistentry>
+								<varlistentry><term>stdword</term> 
+									<listitem>
+										<para>text: the standardized replacement word</para>
+									</listitem>
+								</varlistentry>
+								<varlistentry><term>token</term> 
+									<listitem>
+										<para>integer: the kind of word it is.  Only if it is used in this context will it be replaced. Refer to <ulink url="http://www.pagcgeo.org/docs/html/pagc-12.html#--i-tok--">PAGC Tokens</ulink>.</para>
+									</listitem>
+								</varlistentry>
+						</variablelist>
+						
+					
+						
 					</refsection>
 				</refentry>
   </sect1>
@@ -257,7 +343,7 @@ into includes in the future for easier maintenance.</para></listitem>
 		<refsection>
 			<title>See Also</title>
 	
-			<para><xref linkend="stdaddr" /></para>
+			<para><xref linkend="stdaddr" />, <xref linkend="rulestab" />, <xref linkend="lextab" />, , <xref linkend="gaztab" /></para>
 		</refsection>
 	</refentry>