[postgis-tickets] [PostGIS] #3045: &&& operator confuses dimensions

[PostGIS]

#3045: &&& operator confuses dimensions
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.7
Component:  postgis  |     Version:  2.0.x        
 Keywords:           |  
---------------------+------------------------------------------------------
Description changed by strk:

Old description:

> The &&& operator does not distinguish between Z and M values,
> see this:
> {{{
> WITH v(i,g) AS ( VALUES
>  (1,'POINT(0 0)'::geometry),
>  (2,'POINTZ(0 0 1)'), ---- X (wrong)
>  (3,'POINTZ(0 0 0)'),
>  (4,'POINTM(0 0 1)'), ---- X
>  (5,'POINTZM(0 0 0 1)'),
>  (6,'POINTZM(0 0 1 0)') -- X (wrong)
>  )
> SELECT i FROM v WHERE g &&& 'POINTM(0 0 1)'::geometry;
> }}}

New description:

 The &&& operator does not distinguish between Z and M values,
 see this:
 {{{
 WITH v(i,g) AS ( VALUES
  (1,'POINT(0 0)'::geometry),
  (2,'POINTZ(0 0 1)'), ----- true
  (3,'POINTZ(0 0 0)'), ----- false (wrong?)
  (4,'POINTM(0 0 1)'), ----- true
  (5,'POINTZM(0 0 0 1)'), -- false (wrong!)
  (6,'POINTZM(0 0 1 0)') --- true (wrong!)
  )
 SELECT i FROM v WHERE g &&& 'POINTM(0 0 1)'::geometry;
 }}}

--

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/3045#comment:3>
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.