Ticket #602 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

[raster] Make sure ST_BandNoDataValue return NULL when ST_HasNoDataValue is false

Reported by: pracine Owned by: jorgearevalo
Priority: medium Milestone: PostGIS 2.0.0
Component: raster Version: trunk
Keywords: Cc:

Description


Change History

Changed 3 years ago by pracine

  • status changed from new to assigned

Changed 2 years ago by pracine

  • owner changed from pracine to jorgearevalo
  • status changed from assigned to new

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.

Changed 2 years ago by jorgearevalo

  • status changed from new to assigned

Changed 2 years ago by jorgearevalo

  • status changed from assigned to closed
  • resolution set to fixed

Solved in r6621.

Changed 2 years ago by pracine

So Robe,

following this change ST_SetBandHasNodataValue & ST_BandHasNodataValue do not exist anymore. They are respectively replaced by

ST_SetBandNodataValue(rast, NULL) & NOT ST_BandNodatavalue(rast) IS NULL

Note: See TracTickets for help on using tickets.