From: Regina Obe Date: Sat, 27 Oct 2012 05:53:31 +0000 (+0000) Subject: more ids and descriptive titles X-Git-Tag: 2.1.0beta2~446 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5bff7be36fc633213e3e79aee5421347dbd0d97f;p=postgis more ids and descriptive titles git-svn-id: http://svn.osgeo.org/postgis/trunk@10575 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml index c5f53ac44..69b46575b 100644 --- a/doc/using_postgis_dataman.xml +++ b/doc/using_postgis_dataman.xml @@ -1695,8 +1695,8 @@ AND ST_Relate(a.geom, b.geom, '102101FF2'); - - Loading GIS Data + + Loading GIS (Vector) Data Once you have created a spatial table, you are ready to upload GIS data to the database. Currently, there are two ways to get data into a @@ -1704,7 +1704,7 @@ AND ST_Relate(a.geom, b.geom, '102101FF2'); Shape file loader/dumper. - Using SQL + Loading Data Using SQL If you can convert your data to a text representation, then using formatted SQL might be the easiest way to get your data into PostGIS. As @@ -1985,7 +1985,7 @@ COMMIT; - + Retrieving GIS Data Data can be extracted from the database using either SQL or the @@ -1994,7 +1994,7 @@ COMMIT; tables. - Using SQL + Using SQL to Retrieve Data The most straightforward means of pulling data out of the database is to use a SQL select query to reduce the number of RECORDS and COLUMNS returned