From: Sandro Santilli Date: Sun, 12 Mar 2017 11:12:36 +0000 (+0000) Subject: Topology is enable by default since PostGIS-2.0 (2012) X-Git-Tag: 2.4.0alpha~151 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=60a82f7059f5eee0c0fcdee363ff171df7e02bb0;p=postgis Topology is enable by default since PostGIS-2.0 (2012) git-svn-id: http://svn.osgeo.org/postgis/trunk@15333 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/extras_topology.xml b/doc/extras_topology.xml index 52fc73fc5..1f37f3abe 100644 --- a/doc/extras_topology.xml +++ b/doc/extras_topology.xml @@ -10,7 +10,7 @@ Details of this project can be found at PostGIS Topology Wiki All functions and tables associated with this module are installed in a schema called topology. Functions that are defined in SQL/MM standard are prefixed with ST_ and functions specific to PostGIS are not prefixed. - To build PostGIS 2.0 with topology support, compile with the --with-topology option as described in . Some functions depend on GEOS 3.3+ so you should compile with GEOS 3.3+ to fully utilize the topology support. + 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 diff --git a/doc/installation.xml b/doc/installation.xml index 9758d8c6c..3c73bbcef 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -526,10 +526,10 @@ tar -xvzf postgis-&last_release_version;.tar.gz - --with-topology + --without-topology - 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. @@ -1403,7 +1403,7 @@ All 2 tests passed. You can later run uninstall_legacy.sql to get rid of the deprecated functions after you are done with restoring and cleanup. - + Create a spatially-enabled database without using extensions @@ -1582,12 +1582,12 @@ the folder where the loader extracts the downloaded tiger data.Then run the 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: psql -c "SELECT Loader_Generate_Nation_Script('debbie')" -d geocoder -tA > /gisdata/nation_script_load.sh - + Run the generated nation load commandline scripts. cd /gisdata sh nation_script_load.sh - + After you are done running the nation script, you should have three tables in your tiger_data schema and they should be filled with data. Confirm you do by doing the following queries from psql or pgAdmin SELECT count(*) FROM tiger_data.county_all; count @@ -1602,9 +1602,9 @@ sh nation_script_load.sh (1 row) - + For each state you want to load data for, generate a state 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. - + psql -c "SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie')" -d geocoder -tA > /gisdata/ma_load.sh Run the generated commandline scripts.