[postgis-tickets] [PostGIS] #3069: Some functions inject a bounding box to POINT geometries

[PostGIS]

#3069: Some functions inject a bounding box to POINT geometries
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  high     |   Milestone:  PostGIS 2.0.7
Component:  postgis  |     Version:  2.0.x        
 Keywords:           |  
---------------------+------------------------------------------------------
 I've found that some functions result in points being equipped with a
 bounding box cache. I think this should be avoided by policy, shouldn't it
 ?

 Example:
 {{{
 =# select st_summary(ST_FlipCoordinates('POINT(0 0)'));
 Point[B]
 =# select st_summary(ST_Reverse('POINT(0 0)'));
 Point[B]
 =# select st_summary(postgis_noop('POINT(0 0)'::geometry));
 Point[B]
 }}}

 Actually I start thinking if _all_ the functions would be doing that...

 Standard input functions, correctly, do not add a bbox cache:
 {{{
 =# select st_summary('POINT(0 0)'::geometry);
 Point[]
 =# select st_summary(st_geomfromtext('POINT(0 0)'));
 Point[]
 }}}

 I've tested 1.5 and it is NOT affected. 2.0 branch is affected.
 I'm considering this high because grows the size of POINT layers by a big
 amount (48 bytes instead of 21 for a 2D point)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/3069>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.