From c7d2f96bede7b6b569f57192f71c36921fefeb35 Mon Sep 17 00:00:00 2001
From: Regina Obe <lr@pcorp.us>
Date: Wed, 9 Dec 2009 05:08:52 +0000
Subject: [PATCH] Correct the output type of ST_Extent and flag this as a
 change in behavior in PostGIS 1.4

git-svn-id: http://svn.osgeo.org/postgis/trunk@4992 b70326c6-7e19-0410-871a-916f4a2858ee
---
 doc/reference_misc.xml | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/reference_misc.xml b/doc/reference_misc.xml
index 52fe55766..19d01e162 100644
--- a/doc/reference_misc.xml
+++ b/doc/reference_misc.xml
@@ -311,7 +311,7 @@ SELECT ST_Expand(CAST('BOX3D(778783 2951741 1,794875 2970042.61545891 10)' As bo
 	  <refsynopsisdiv>
 		<funcsynopsis>
 		  <funcprototype>
-			<funcdef>box2d <function>ST_Extent</function></funcdef>
+			<funcdef>box3d_extent <function>ST_Extent</function></funcdef>
 			<paramdef><type>geometry set</type> <parameter>geomfield</parameter></paramdef>
 		  </funcprototype>
 		</funcsynopsis>
@@ -331,7 +331,11 @@ SELECT ST_Expand(CAST('BOX3D(778783 2951741 1,794875 2970042.61545891 10)' As bo
 		</note>
 
 		<note>
-		  <para>Bounding boxes of all geometries are currently 2-d even if they are 3-dimensional geometries.</para>
+		  <para>ST_Extent will return boxes with only an x and y component even with (x,y,z) coordinate geometries.  To maintain x,y,z use ST_Extent3D instead.</para>
+		</note>
+		
+		<note>
+		  <para>Availability: 1.4.0 As of 1.4.0 now returns a box3d_extent instead of box2d object.</para>
 		</note>
 
 	  </refsection>
@@ -371,7 +375,7 @@ SELECT ST_SetSRID(ST_Extent(the_geom),2249) as bextent FROM sometable;
 
 	  <refsection>
 		<title>See Also</title>
-		<para><xref linkend="ST_AsEWKT" />, <xref linkend="ST_SetSRID" />, <xref linkend="ST_SRID" /></para>
+		<para><xref linkend="ST_AsEWKT" />, <xref linkend="ST_Extent3D" />, <xref linkend="ST_SetSRID" />, <xref linkend="ST_SRID" /></para>
 	  </refsection>
 	</refentry>
 
-- 
2.40.0