[postgis-tickets] r15333 - Topology is enable by default since PostGIS-2.0 (2012)

[Sandro Santilli]

Author: strk
Date: 2017-03-12 04:12:36 -0700 (Sun, 12 Mar 2017)
New Revision: 15333

Modified:
   trunk/doc/extras_topology.xml
   trunk/doc/installation.xml
Log:
Topology is enable by default since PostGIS-2.0 (2012)

Modified: trunk/doc/extras_topology.xml
===================================================================
--- trunk/doc/extras_topology.xml	2017-03-12 08:40:41 UTC (rev 15332)
+++ trunk/doc/extras_topology.xml	2017-03-12 11:12:36 UTC (rev 15333)
@@ -10,7 +10,7 @@
 	<para>Details of this project can be found at <ulink url="http://trac.osgeo.org/postgis/wiki/UsersWikiPostgisTopology">PostGIS Topology Wiki</ulink></para>
 	<para>All functions and tables associated with this module are installed in a schema called <varname>topology</varname>.</para>
 	<para>Functions that are defined in SQL/MM standard are prefixed with ST_ and functions specific to PostGIS are not prefixed.</para>
-	<para>To build PostGIS 2.0 with topology support, compile with the --with-topology option as described in <xref linkend="postgis_installation"/>.  Some functions depend on GEOS 3.3+ so you should compile with GEOS 3.3+ to fully utilize the topology support.</para>
+	<para>Topolgy support is build by default starting with PostGIS 2.0, and can be disabled specifying --without-topology configure option at build time as described in <xref linkend="postgis_installation"/></para>
 
 	<sect1 id="Topology_Types">
         <sect1info>

Modified: trunk/doc/installation.xml
===================================================================
--- trunk/doc/installation.xml	2017-03-12 08:40:41 UTC (rev 15332)
+++ trunk/doc/installation.xml	2017-03-12 11:12:36 UTC (rev 15333)
@@ -526,10 +526,10 @@
 		  </listitem>
 		</varlistentry>
 		<varlistentry>
-		  <term><command>--with-topology</command></term>
+		  <term><command>--without-topology</command></term>
 		  <listitem>
 			<para>
-			  Compile with topology support.  This will build the topology.sql file.  There is no corresponding library
+			  Disable topology support. There is no corresponding library
 			  as all logic needed for topology is in postgis-&last_release_version; library.
 			</para>
 		  </listitem>
@@ -1403,7 +1403,7 @@
 
 	<para>You can later run <filename>uninstall_legacy.sql</filename> to get rid of the deprecated functions after you are done with restoring and cleanup.</para>
   </sect1>
-  
+
     <sect1 id="create_new_db">
 	<title>Create a spatially-enabled database without using extensions</title>
 
@@ -1582,12 +1582,12 @@
 			<listitem><para>Then run the  <xref linkend="Loader_Generate_Nation_Script" />  SQL function make sure to use the name of your custom profile and copy the script to a .sh or .bat file.  So for example to build  the nation load:</para>
 					<programlisting>psql -c "SELECT Loader_Generate_Nation_Script('debbie')" -d geocoder -tA > /gisdata/nation_script_load.sh</programlisting>
 			</listitem>
-			
+
 			<listitem><para>Run the generated nation load commandline scripts.</para>
 				<programlisting>cd /gisdata
 sh nation_script_load.sh</programlisting>
       </listitem>
-      
+
       <listitem><para>After you are done running the nation script, you should have three tables in your <code>tiger_data</code> schema and they should be filled with data. Confirm you do by doing the following queries from psql or pgAdmin</para>
 				<programlisting>SELECT count(*) FROM tiger_data.county_all;</programlisting>
 <screen> count
@@ -1602,9 +1602,9 @@
 (1 row)
 </screen>
       </listitem>
-			
+
 			<listitem><para>For each state you want to load data for, generate a state script <xref linkend="Loader_Generate_Script" />.  DO NOT Generate the state script until you have already loaded the nation data, because the state script utilizes county list loaded by nation script.</para></listitem>
-			
+
 			<listitem><programlisting>psql -c "SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie')" -d geocoder -tA > /gisdata/ma_load.sh</programlisting></listitem>
 
 			<listitem><para>Run the generated commandline scripts.</para>