[postgis-tickets] [PostGIS] #3283: Corrupt cached bboxes gets created (m-value)

[PostGIS]

#3283: Corrupt cached bboxes gets created (m-value)
----------------------+---------------------------
  Reporter:  nicklas  |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.2.0
 Component:  postgis  |    Version:  trunk
Resolution:           |   Keywords:  temporal
----------------------+---------------------------

Comment (by robe):

 SAme result here.  What I don't understand is why adding the bbox back
 gives a slightly different error message.  It's almost like we have two
 separate cache box adders and the one on restore is different from the
 add_bbox one.

 When I do this:


 {{{

 select st_cpawithin(
 (select PostGIS_AddBBox(PostGIS_DropBBox(geom)) from p where gid = 1 and
 ST_IsValidTrajectory(geom))
 ,
 (select PostGIS_AddBBox(PostGIS_DropBBox(geom)) from p where gid = 2 and
 ST_IsValidTrajectory(geom))
 ,1000);
 }}}

 I get:

 {{{
 ERROR:  Could not find point with M=9.28441e-309 on first geom
 ********** Error **********

 ERROR: Could not find point with M=9.28441e-309 on first geom
 SQL state: XX000


 }}}


 But with just restoring, I got the same M=0 error message you got.  I know
 they are off by a smidge so could be just some windows artifact.


 This is testing on:


 {{{
 PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 64-bit
 POSTGIS="2.2.0dev r14083" GEOS="3.5.0-CAPI-1.9.0 r4088" PROJ="Rel. 4.9.1,
 04 March 2015" GDAL="GDAL 2.0.0, released 2015/06/14" LIBXML="2.7.8"
 LIBJSON="0.12" RASTER
 }}}

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3283#comment:2>
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.