Opened 14 years ago
Closed 13 years ago
#1049 closed task (fixed)
[raster] ST_SetBandNoDataValue change to use default args
| Reported by: | robe | Owned by: | pracine |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.0 |
| Component: | raster | Version: | master |
| Keywords: | Cc: |
Description
I've already updated the documentation as if it uses default args, but can you merge:
st_setbandnodatavalue(rast raster, band integer, nodatavalue double precision, forcechecking boolean)
st_setbandnodatavalue(rast raster, band integer, nodatavalue double precision)
to just:
st_setbandnodatavalue(rast raster, band integer, nodatavalue double precision, forcechecking boolean DEFAULT false)
Also I forgot — what exactly does the forcechecking argument do when set to true?
Change History (2)
comment:1 by , 14 years ago
| Summary: | ST_SetBandNoDataValue change to use default args → [raster] ST_SetBandNoDataValue change to use default args |
|---|
comment:2 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
If forcechecking is TRUE, the band specified is inspected pixel by pixel to see if all pixels are NODATA. If all pixels are NODATA, a special band flag "isnodata" is set to TRUE.
I'm closing this ticket as the changes requested in this ticket was done in r8218.