[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 pramsey):

 Just to be precise about numbers, the actual min/max M values are this:
 {{{
     min     |    max     | gid
 ------------+------------+-----
  1441014776 | 1441029714 |   1
  1440992184 | 1441014568 |   2
 }}}
 Gathered by dumping the points and getting their extrema. And the actual
 values of the bounding boxes coming in from the cache are:
 {{{
 (lldb) p *g1->bbox
 (GBOX) $2 = (flags = '\x06', xmin = 332854.125, xmax = 333364.5625, ymin =
 6726488.5, ymax = 6726756, zmin = 7.2911292855948646E-304, zmax = 0, mmin
 = 1441014656, mmax = 1441029760)
 (lldb) p *g2->bbox
 (GBOX) $4 = (flags = '\x06', xmin = 332893.0625, xmax = 333092.53125, ymin
 = 6726633, ymax = 6726818.5, zmin = 7.2911292855948646E-304, zmax = 0,
 mmin = 1440992128, mmax = 1441014656)
 }}}
 Now, remember that bounding boxes are rounding outwards slightly so they
 are always a little overdetermined, but not in ways that are usually
 visible. But in this case we are dealing with quite large absolute values,
 so I think the outward rounding is visible.

 I just monkey-patched at r14089

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