#602 closed enhancement (fixed)
[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: | master |
Keywords: | Cc: |
Description
Change History (5)
comment:1 by , 14 years ago
Status: | new → assigned |
---|
comment:2 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
comment:3 by , 14 years ago
Status: | new → assigned |
---|
comment:5 by , 14 years ago
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.
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.