[postgis-devel] [PostGIS] #1536: [raster] There should be an option for setting the nodata value in certain variants of ST_Intersection(raster, raster)
PostGIS
trac at osgeo.org
Mon Feb 27 11:09:57 PST 2012
#1536: [raster] There should be an option for setting the nodata value in certain
variants of ST_Intersection(raster, raster)
---------------------+------------------------------------------------------
Reporter: pracine | Owner: pracine
Type: defect | Status: assigned
Priority: low | Milestone: PostGIS 2.0.0
Component: raster | Version: trunk
Keywords: |
---------------------+------------------------------------------------------
Comment(by pracine):
I redesigned the variants if I add a double precision[] nodataval
parameter. I end up with: (= means this parameter has a default value. I
shortened everything for ease of reading)
-- raster/geometry[[BR]]
rast, geom, reg[[BR]]
rast, geom, nodata=, reg=[[BR]]
rast, band, geom, reg[[BR]]
rast, band, geom, nodata=, reg=
-- raster/raster no band number[[BR]]
ras1, rast2, return=, nodaval[]=, reg=[[BR]]
ras1, rast2, return=, nodaval=, reg=[[BR]]
ras1, rast2, nodaval[], reg= (opt)[[BR]]
ras1, rast2, nodaval, reg= (opt)[[BR]]
ras1, rast2, reg (opt)
-- raster/raster with band number[[BR]]
ras1, b1, rast2, b2, return=, nodaval[]=, reg=[[BR]]
ras1, b1, rast2, b2, return=, nodaval=, reg=[[BR]]
ras1, b1, rast2, b2, nodaval[], reg= (opt)[[BR]]
ras1, b1, rast2, b2, nodaval, reg= (opt)[[BR]]
ras1, b1, rast2, b2, reg (opt)
Maybe we can simplify by removing the three last one (the opt ones) of the
two last groups and force users to pass something or a casted NULL in one
of the two first one?
Could we, in the doc, when we have parameter accepting a single value or
an array, like here the new nodataval parameter, not list the variants
accepting an array and simply say in the doc "Every of those variant also
accept an array of value"?
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1536#comment:26>
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.
More information about the postgis-devel
mailing list