[postgis-tickets] [PostGIS] #3620: Garden regression with ST_MinimumBoundingCircle

[PostGIS]

#3620: Garden regression with ST_MinimumBoundingCircle
---------------------+---------------------------
 Reporter:  robe     |      Owner:  pramsey
     Type:  defect   |     Status:  new
 Priority:  medium   |  Milestone:  PostGIS 2.3.0
Component:  postgis  |    Version:  trunk
 Keywords:           |
---------------------+---------------------------
 In comparing Garden answers between 2.2.2 and 2.3.0, see a difference in
 Minimum Bounding circle when applied to point.

 I think this may be a side-effect of a different change and is not
 technically less wrong than the previous answer.

 So might just require breaking change notice in docs and NEWs.


 In PostGIS 2.2.2
 {{{
 SELECT ST_AsText(ST_MinimumBoundingCircle( ST_Point(10,2),3 ));

 --returns back the point

   st_astext
 -------------
  POINT(10 2)
 }}}


 In PostGIS 2.3.0dev r15053 returns and empty geometry

 {{{
 SELECT ST_AsText(ST_MinimumBoundingCircle( ST_Point(10,2),3 ));

 --returns back an empty polygon

    st_astext
 ---------------
  POLYGON EMPTY
 (1 row)
 }}}

 Given there is no way to get a bounding circle from a point aside from
 doing some buffering tricks. I'm okay with eitehr.

 Well I suppose on one hand 2.3.0dev at least returns a polygon though less
 information.  I'm okay either way as long as we document this change for
 people expecting to get a non-empty answer back.

 I'm also seeing different answers with a couple other
 ST_MinimumBoundingCircle
 LINESTRING, POLYGON, MULTISURFACE, CIRCULARSTRING, CURVEPOLYGON.

 I didn't even know we had support for CURVES, on ST_MinimumBoundingCircle
 (but I guess as a result of that other change with CURVES that made curve
 support for a bunch of functions in 2.2.

 Anyrate these I haven't looked at.  They may be very well corrections, or
 slight artifacts of change in process, so may be ignorable.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3620>
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.