[postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s

codesite-noreply at google.com codesite-noreply at google.com
Fri Jan 9 02:45:10 PST 2009


Status: Accepted
Owner: mark.cav... at siriusit.co.uk
Labels: Milestone-1.4

New issue 93 by mark.cav... at siriusit.co.uk: ST_Extent() and  
ST_Estimated_Extent() return BOX2DFLOAT4s
http://code.google.com/p/postgis/issues/detail?id=93

In the case of ST_Extent(), this is serious because it means that
ST_Extent(col) will never return the exact extent of a column - it will
always be inflated by a small amount due to the extra conversion between
BOX3D and BOX2DFLOAT4.

* BOX2DFLOAT4s should never be exposed to the user, especially in that
ST_Extent() returns a string containing BOX (a legacy PostgreSQL type)
rather than BOX3D *

ST_Estimated_Extent() should also return a string beginning "BOX3D" for the
same reason.




--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings



More information about the postgis-devel mailing list