From: Regina Obe <lr@pcorp.us>
Date: Tue, 29 Sep 2009 06:34:48 +0000 (+0000)
Subject: Add a new special index section to collect functions that take as input or output... 
X-Git-Tag: 1.5.0b1~471
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6234fd0124b06fb275abb8c045a03a878bc86ed6;p=postgis

Add a new special index section to collect functions that take as input or output geography data type.  Also give pretty anchor to PostGIS Geography section

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

diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml
index 54f943b08..1deff45d6 100644
--- a/doc/using_postgis_dataman.xml
+++ b/doc/using_postgis_dataman.xml
@@ -169,7 +169,7 @@ geometry
 (1 row)</programlisting>
 	</sect2>
 
-	<sect2>
+	<sect2 id="PostGIS_Geography">
 	  <title>PostGIS Geography Type</title>
 
 	  <para>The geography type provides native support for spatial features represented on "geographic" coordinates (sometimes called "geodetic" coordinates, or "lat/lon", or "lon/lat"). Geographic coordinates are spherical coordinates expressed in angular units (degrees). </para>
@@ -187,9 +187,9 @@ geometry
 
 	  <para>The new geography type uses the PostgreSQL 8.3+ typmod definition format so that a table with a geography field
 			can be added in a single step.  All the standard OGC formats except for curves are supported.</para>
-			
+
 	<para>Geography Basics</para>
- 
+
 
 
 	 <para>The geography type only supports the simplest of simple features. Standard geometry type data will autocast to geography if it is of SRID 4326.  You can also use the EWKT and EWKB
@@ -222,17 +222,17 @@ geometry
 		</listitem>
 		<!-- TODO: Add other examples -->
 		</itemizedlist>
-	  	<para>The new geography fields don't get registered in the geometry_columns.  They get registered in a new view called
-				geography_columns which is a view against the system catalogs so is always automatically kept up to date without need 
+		<para>The new geography fields don't get registered in the geometry_columns.  They get registered in a new view called
+				geography_columns which is a view against the system catalogs so is always automatically kept up to date without need
 					for an AddGeom... like function.</para>
-				
+
 		<para>Now, check the "geography_columns" view and see that your table is listed:</para>
 
 		<para><programlisting>SELECT * FROM geography_columns;</programlisting></para>
 
 		<para>Using Input/Output Functions</para>
 
-		<para>There are only four intput/output functions at this time supporting the OGC well-known text (WKT) and well-known binary (WKB) formats. 
+		<para>There are only four intput/output functions at this time supporting the OGC well-known text (WKT) and well-known binary (WKB) formats.
 		Adding further output formats (GML, GeoJSON) should be straight-forward, borrowing code from the geometry implementations.</para>
 
 		<itemizedlist>
diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl
index 60bd45641..db9ff4cb0 100644
--- a/doc/xsl/postgis_aggs_mm.xml.xsl
+++ b/doc/xsl/postgis_aggs_mm.xml.xsl
@@ -70,6 +70,35 @@
 				</itemizedlist>
 		</sect1>
 
+		<sect1 id="PostGIS_GeographyFunctions">
+			<title>PostGIS Geography Support Functions</title>
+			<para>The functions and operators given below are PostGIS functions/operators that take as input or return as output a <link linkend="PostGIS_Geography">geography</link> data type object.</para>
+				<itemizedlist>
+			<!-- Pull out the purpose section for each ref entry and strip whitespace and put in a variable to be tagged unto each function comment  -->
+				<xsl:for-each select='sect1/refentry'>
+					<xsl:sort select="@id"/>
+					<xsl:variable name='comment'>
+						<xsl:value-of select="normalize-space(translate(translate(refnamediv/refpurpose,'&#x0d;&#x0a;', ' '), '&#09;', ' '))"/>
+					</xsl:variable>
+					<xsl:variable name="refid">
+						<xsl:value-of select="@id" />
+					</xsl:variable>
+					<xsl:variable name="refname">
+						<xsl:value-of select="refnamediv/refname" />
+					</xsl:variable>
+
+			<!-- For each proto function accepts or returns a geography -->
+					<xsl:for-each select="refsynopsisdiv/funcsynopsis/funcprototype">
+						<xsl:choose>
+							<xsl:when test="contains(paramdef/type,'geography') or contains(funcdef,'geography')">
+								<listitem><link linkend="{$refid}"><xsl:value-of select="$refname" /></link> - <xsl:value-of select="$comment" /></listitem>
+							</xsl:when>
+						</xsl:choose>
+					</xsl:for-each>
+				</xsl:for-each>
+				</itemizedlist>
+		</sect1>
+
 		<sect1 id="PostGIS_3D_Functions">
 			<title>PostGIS Functions that support 3D</title>
 			<para>The functions given below are PostGIS functions that do not throw away the Z-Index.</para>
@@ -126,6 +155,8 @@
 				</itemizedlist>
 		</sect1>
 
+
+
 		<sect1 id="NewFunctions">
 			<title>New PostGIS Functions</title>
 			<sect2 id="NewFunctions_1_5">
@@ -141,7 +172,7 @@
 						<xsl:variable name="refid">
 							<xsl:value-of select="@id" />
 						</xsl:variable>
-	
+
 				<!-- For each section if there is note about availability in this version -->
 							<xsl:for-each select="refsection">
 								<xsl:for-each select="para">
@@ -168,7 +199,7 @@
 						<xsl:variable name="refid">
 							<xsl:value-of select="@id" />
 						</xsl:variable>
-	
+
 				<!-- For each section if there is note about availability in this version -->
 							<xsl:for-each select="refsection">
 								<xsl:for-each select="para|note">