[postgis-devel] [PostGIS] #1639: [raster] MapAlgebraExpr can't handle conditions

[PostGIS]

#1639: [raster] MapAlgebraExpr can't handle conditions
----------------------+-----------------------------------------------------
  Reporter:  nicklas  |       Owner:  pracine      
      Type:  defect   |      Status:  closed       
  Priority:  high     |   Milestone:  PostGIS 2.0.0
 Component:  raster   |     Version:  trunk        
Resolution:  fixed    |    Keywords:               
----------------------+-----------------------------------------------------

Comment(by dustymugs):

 In the C code, all pixels are expressed and worked on as double precision
 values.  When it comes time to store a value, the value is
 clamped/truncated to band's pixel type.  I suppose that when the raster
 project started that a union variable could have been used for working
 with a pixel but that adds its own bag of nightmares.

 And yes, it is does look like a long way to go for a simple boolean.
 Sadly, the choices are simplicity or flexibility and we picked
 flexibility.

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