more clarification of behavior change in 2.0 of bbox storage

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

diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl
index fc984dd18bddabdcb6024f44e19fa55e25a4da2a..856745c54f46c9ab92ab648e15350417c1aa3538 100644 (file)
--- a/doc/xsl/postgis_aggs_mm.xml.xsl
+++ b/doc/xsl/postgis_aggs_mm.xml.xsl
@@ -506,6 +506,10 @@
                         or some internal functions that were never documented.  If you are using a function that you don't see documented,
                         it's probably deprecated, about to be deprecated, or internal and should be avoided.  If you have applications or tools
                         that rely on deprecated functions, please refer to <link linked="legacy_faq" /> for more details.</para></note>
+                    <note><para>Bounding boxes of geometries have been changed from float4 to double precision (float8).  This has an impact
+                       on answers you get using bounding box operators and casting of bounding boxes to geometries. E.g ST_SetSRID(abbox) will
+                       often return a different more accurate answer in PostGIS 2.0+ than it did in prior versions which may very well slightly
+                       change answers to view port queries.</para></note>
                     <note><para>The arguments hasnodata was replaced with exclude_nodata_value which has the same meaning as the older hasnodata but clearer in purpose.</para></note>
                     <itemizedlist>
                     <!-- Pull out the purpose section for each ref entry   -->