using (T) to denote Paul's transform hacks and noting what that (T) means. Will...

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

diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl
index bcb3872386b77c481c88cc8365824c07777a17d2..63d0f52990119bf532503ddd22f9ebd9db343d53 100644 (file)
--- a/doc/xsl/postgis_aggs_mm.xml.xsl
+++ b/doc/xsl/postgis_aggs_mm.xml.xsl
@@ -73,6 +73,8 @@
                <sect1 id="PostGIS_GeographyFunctions">\r
                        <title>PostGIS Geography Support Functions</title>\r
                        <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>\r
+                       <note><para>Functions with a (T) are not native geodetic functions, and use a ST_Transform call to and from geometry to do the operation.  As a result, they may not behave as expected when going over dateline, poles, \r
+                               and for large geometries or geometry pairs that cover more than one UTM zone. Basic tranform - (favoring UTM, polar stereographic and falling back on mercator in worst case scenario)</para></note>\r
                                <itemizedlist>\r
                        <!-- Pull out the purpose section for each ref entry and strip whitespace and put in a variable to be tagged unto each function comment  -->\r
                                <xsl:for-each select='sect1/refentry'>\r