[postgis-devel] [PostGIS] #602: [raster] Make sure ST_BandNoDataValue return NULL when ST_HasNoDataValue is false

[PostGIS]

#602: [raster] Make sure ST_BandNoDataValue return NULL when ST_HasNoDataValue is
false
----------------------------+-----------------------------------------------
 Reporter:  pracine         |       Owner:  jorgearevalo 
     Type:  enhancement     |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by pracine):

  * owner:  pracine => jorgearevalo
  * status:  assigned => new


Comment:

 Also:

 -Make sure ST_SetBandNodataValue accept NULL as input
 -Get rid of ST_SetBandHasNodataValue
 -Get rid of ST_BandHasNodataValue and all dependencies. It should be
 replaced in plpgsql by (ST_BandNodataValue(rast, band) IS NULL)

 Note that, ST_BandNoDataValue in order to know if the nodata value is
 significant, still need the flag added when implementing
 ST_SetBandHasNodataValue. The difference is that now ST_SetBandNodataValue
 controls the flag.

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