From: Kevin Neufeld <kneufeld.ca@gmail.com>
Date: Fri, 27 Nov 2009 17:06:51 +0000 (+0000)
Subject: Fixed a few typos and missing references
X-Git-Tag: 1.5.0b1~168
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d673ed980824b9f06f73551c47b03ab2d0b5753b;p=postgis

Fixed a few typos and missing references

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

diff --git a/doc/reference_processing.xml b/doc/reference_processing.xml
index 1bd2cdccc..d17cde6e3 100644
--- a/doc/reference_processing.xml
+++ b/doc/reference_processing.xml
@@ -817,29 +817,26 @@ MULTIPOINT(-118.6 38.329 6,-118.58 38.38 5)
 			<para>Availability: PostGIS 1.0.0RC1. Requires PostgreSQL 7.3 or higher.</para>
 			<note><para>Prior to 1.3.4, this function crashes if used with geometries that contain CURVES.  This is fixed in 1.3.4+</para></note>
 
-			<para>Z_support;</para>
-			<para>curve_support;</para>
+			<para>&Z_support;</para>
+			<para>&curve_support;</para>
 	  </refsection>
 
 	  <refsection>
 		<title>Examples</title>
 	<programlisting>SELECT sometable.field1, sometable.field1,
-	  (ST_Dump(sometable.the_geom)).geom As the_geom
+      (ST_Dump(sometable.the_geom)).geom AS the_geom
 FROM sometable;
 
 --Break a compound curve into its constituent linestrings and circularstrings
 SELECT ST_AsEWKT(a.geom), ST_HasArc(a.geom)
-  FROM ( SELECT (ST_Dump(p_geom)).geom as geom
-		   FROM (SELECT ST_GeomFromEWKT('COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))') as p_geom) as b
-	   ) as a;
-		  st_asewkt          | st_hasarc
+  FROM ( SELECT (ST_Dump(p_geom)).geom AS geom
+         FROM (SELECT ST_GeomFromEWKT('COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))') AS p_geom) AS b
+        ) AS a;
+          st_asewkt          | st_hasarc
 -----------------------------+----------
  CIRCULARSTRING(0 0,1 1,1 0) | t
  LINESTRING(1 0,0 1)         | f
-(2 rows)
-
-
-</programlisting>
+(2 rows)</programlisting>
 	  </refsection>
 	  <refsection>
 		<title>See Also</title>
@@ -1147,8 +1144,8 @@ FROM country
 		<para>Converts plain LINESTRING/POLYGONS to CIRCULAR STRINGs and Curved Polygons.  Note much fewer points are needed to describe the curved equivalent.</para>
 
 		<para>Availability: 1.2.2?</para>
-		<para>Z_support;</para>
-		<para>curve_support;</para>
+		<para>&Z_support;</para>
+		<para>&curve_support;</para>
 	  </refsection>
 
 
diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml
index cdfbad482..a79652139 100644
--- a/doc/using_postgis_dataman.xml
+++ b/doc/using_postgis_dataman.xml
@@ -942,12 +942,12 @@ FROM public.myschema.myspecialpois LIMIT 1;
 -- by returning false if a LinearRing (start and end points are the same)
 -- has less than 2 vertices.
 gisdb=# SELECT
-   st_isvalid('LINESTRING(0 0, 1 1)'),
-   st_isvalid('LINESTRING(0 0, 0 0)');
+   ST_IsValid('LINESTRING(0 0, 1 1)'),
+   ST_IsValid('LINESTRING(0 0, 0 0)');
 
  st_isvalid | st_isvalid
-------------+---------
-	  t     |     f</programlisting>
+------------+-----------
+      t     |     f</programlisting>
 
 	  <para>By default, PostGIS does not apply this validity check on geometry
 	  input, because testing for validity needs lots of CPU time for complex
@@ -957,7 +957,7 @@ gisdb=# SELECT
 
 	  <programlisting>ALTER TABLE mytable
   ADD CONSTRAINT geometry_valid_check
-	CHECK (isvalid(the_geom));</programlisting>
+	CHECK (ST_IsValid(the_geom));</programlisting>
 
 	  <para>If you encounter any strange error messages such as "GEOS
 	  Intersection() threw an error!" or "JTS Intersection() threw an error!"