[postgis-commits] svn - r2830 - trunk/doc

postgis-commits at postgis.refractions.net postgis-commits at postgis.refractions.net
Mon Jul 7 20:12:08 PDT 2008


Author: kneufeld
Date: 2008-07-07 20:12:08 -0700 (Mon, 07 Jul 2008)
New Revision: 2830

Modified:
   trunk/doc/postgis.xml
Log:
updated tips section to reference ST_* function names

Modified: trunk/doc/postgis.xml
===================================================================
--- trunk/doc/postgis.xml	2008-07-07 12:20:43 UTC (rev 2829)
+++ trunk/doc/postgis.xml	2008-07-08 03:12:08 UTC (rev 2830)
@@ -2682,8 +2682,8 @@
         additional column that "caches" the bbox, and matching against
         this. In our example, the commands are like:</para>
 
-        <programlisting>SELECT addGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2'); 
-UPDATE mytable set bbox = Envelope(Force_2d(the_geom));</programlisting>
+        <programlisting>SELECT AddGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2'); 
+UPDATE mytable SET bbox = ST_Envelope(ST_Force_2d(the_geom));</programlisting>
 
         <para>Now change your query to use the &amp;&amp; operator against
         bbox instead of geom_column, like:</para>
@@ -2737,13 +2737,13 @@
       <title>Avoiding dimension conversion</title>
 
       <para>Sometimes, you happen to have 3D or 4D data in your table, but
-      always access it using OpenGIS compliant asText() or asBinary()
+      always access it using OpenGIS compliant ST_AsText() or ST_AsBinary()
       functions that only output 2D geometries. They do this by internally
-      calling the force_2d() function, which introduces a significant overhead
+      calling the ST_Force_2d() function, which introduces a significant overhead
       for large geometries. To avoid this overhead, it may be feasible to
       pre-drop those additional dimensions once and forever:</para>
 
-      <programlisting>UPDATE mytable SET the_geom = force_2d(the_geom); 
+      <programlisting>UPDATE mytable SET the_geom = ST_Force_2d(the_geom); 
 VACUUM FULL ANALYZE mytable;</programlisting>
 
       <para>Note that if you added your geometry column using



More information about the postgis-commits mailing list