added some xreferences so the autobuild process does not throw errors.

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

diff --git a/doc/reference.xml b/doc/reference.xml
index a14755022ff3bfd751c655f817e85b46132d9262..98ea670dd975821213f117111914aea3d077bb9d 100644 (file)
--- a/doc/reference.xml
+++ b/doc/reference.xml
@@ -380,7 +380,7 @@
       <title>Geometry Accessors</title>
 
       <variablelist>
-        <varlistentry>
+        <varlistentry id="ST_SRID">
           <term>ST_SRID(geometry)</term>
 
           <listitem>
@@ -658,7 +658,7 @@ GROUP BY gid, field1,field2;
       <title>Geometry Constructors</title>
 
       <variablelist>
-        <varlistentry>
+        <varlistentry id="ST_GeomFromText">
                        <term>ST_GeomFromText(text)</term>
                        <term>ST_GeomFromText(text,srid integer)</term>
 
@@ -1454,7 +1454,7 @@ GROUP BY gid, field1,field2;
       <title>Geometry Constructors</title>
 
       <variablelist>
-        <varlistentry>
+        <varlistentry id="ST_GeomFromEWKT">
           <term>ST_GeomFromEWKT(text)</term>
 
           <listitem>
@@ -1462,7 +1462,7 @@ GROUP BY gid, field1,field2;
           </listitem>
         </varlistentry>
 
-        <varlistentry>
+        <varlistentry id="ST_GeomFromEWKB">
           <term>ST_GeomFromEWKB(bytea)</term>
 
           <listitem>
@@ -1544,7 +1544,7 @@ GROUP BY gid, field1,field2;
             into Geometry Collections. Unfortunately geometry collections are
             not well-supported by GIS tools. To prevent ST_Collect from
             returning a Geometry Collection when collecting MULTI geometries,
-            one can use the below trick that utilizes ST_Dump to expand the
+            one can use the below trick that utilizes <xref linkend="ST_Dump" /> to expand the
             MULTIs out to singles and then regroup them.</para>
 
             <programlisting>
@@ -1569,7 +1569,7 @@ GROUP BY stusps
           </listitem>
         </varlistentry>
 
-        <varlistentry>
+        <varlistentry id="ST_Dump">
           <term>ST_Dump(geometry)</term>
 
           <listitem>
@@ -1878,7 +1878,7 @@ z' = z </programlisting> This method is a subcase of the 3D method
           </listitem>
         </varlistentry>
 
-        <varlistentry>
+        <varlistentry id="ST_LineMerge">
           <term>ST_LineMerge(geometry)</term>
 
           <listitem>
@@ -2192,7 +2192,7 @@ WHERE n*100.00/length &lt; 1;
           </listitem>
         </varlistentry>
 
-        <varlistentry id="Accum">
+        <varlistentry id="ST_Accum">
           <term>ST_Accum(geometry set)</term>
 
           <listitem>
@@ -2504,7 +2504,7 @@ WHERE n*100.00/length &lt; 1;
         </listitem>
       </varlistentry>
 
-      <varlistentry>
+      <varlistentry id="ST_IsClosed">
         <term>ST_IsClosed</term>
 
         <listitem>

diff --git a/doc/reference_new.xml b/doc/reference_new.xml
index 2438674205dcb11321033197834713b41e38d614..87fa8dd60384610ae95a89f2511584dadac18840 100644 (file)
--- a/doc/reference_new.xml
+++ b/doc/reference_new.xml
@@ -432,9 +432,9 @@ Check constraints:
                                         <para>Throws an error if WKT is not a MULTILINESTRING. Forces
                                        MULTIPOLYGON output even when result is really only composed by a
                                        single POLYGON; use <link
-                                       linkend="BdPolyFromText">BdPolyFromText</link> if you're sure a
+                                       linkend="ST_BdPolyFromText">ST_BdPolyFromText</link> if you're sure a
                                        single POLYGON will result from operation, or see <link
-                                       linkend="BuildArea">BuildArea()</link> for a postgis-specific
+                                       linkend="ST_BuildArea">ST_BuildArea()</link> for a postgis-specific
                                        approach.</para>
                                </note>
                                
@@ -615,7 +615,7 @@ SELECT userpoints.id, ST_MakeLine(startpoint, endpoint) As drawn_line
             holes. You can construct a geometry array using ST_Accum or the PostgreSQL ARRAY[] and
             ARRAY() constructs. Input geometries must be closed LINESTRINGS.</para>
                        <note>
-                               <para>This function will not accept a MULTILINESTRING.  Use ST_LineMerge or ST_Dump to generate line strings.</para>
+                               <para>This function will not accept a MULTILINESTRING.  Use <xref linkend="ST_LineMerge" /> or <xref linkend="ST_Dump" /> to generate line strings.</para>
                        </note>
                        
                </refsection>
@@ -684,7 +684,7 @@ FROM
                </refsection>
                <refsection>
                        <title>See Also</title>
-                       <para><xref linkend="ST_Accum" />, <xref linkend="ST_AddPoint" />, <xref linkend="ST_GeometryType" />, <xref linkend="ST_IsClose" />, <xref linkend="ST_LineMerge" /></para>
+                       <para><xref linkend="ST_Accum" />, <xref linkend="ST_AddPoint" />, <xref linkend="ST_GeometryType" />, <xref linkend="ST_IsClosed" />, <xref linkend="ST_LineMerge" /></para>
                </refsection>
        </refentry>
   </sect1>
@@ -1411,7 +1411,7 @@ CREATE INDEX idx_the_geom_26986_parcels
                                WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport.
                        </para>
                        <note>
-                         <para>ST_AsEWKT is the reverse of ST_GeomFromEWKT.  Use ST_GeomFromEWKT to convert to a postgis geometry from ST_AsEWKT representation.</para>
+                         <para>ST_AsEWKT is the reverse of <xref linkend="ST_GeomFromEWKT" />.  Use <xref linkend="ST_GeomFromEWKT" /> to convert to a postgis geometry from ST_AsEWKT representation.</para>
                        </note>
                  </refsection>
                
@@ -1458,13 +1458,13 @@ SRID=4326;POLYGON((0 0,0 1,1 1,1 0,0 0))
 
                        <note>
                          <para>The WKT spec does not include the SRID.  To get the SRID as part of the data, use the non-standard
-                               PostGIS ST_AsEWKT()</para>
+                               PostGIS <xref linkend="ST_AsEWKT" /></para>
                        </note>
                        <para><inlinegraphic class="sfs_compliant" fileref="images/warning.png" />
                                WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport.
                        </para>
                        <note>
-                         <para>ST_AsText is the reverse of ST_GeomFromText.  Use ST_GeomFromText to convert to a postgis geometry from ST_AsText representation.</para>
+                         <para>ST_AsText is the reverse of <xref linkend="ST_GeomFromText" />.  Use <xref linkend="ST_GeomFromText" /> to convert to a postgis geometry from ST_AsText representation.</para>
                        </note>
                
                        <!-- Optionally mention OpenGIS compliancy if appropriate -->