[postgis-devel] [PostGIS] #1267: [raster] Add manual height/width support to ST_Resample
PostGIS
trac at osgeo.org
Tue Nov 15 07:06:50 PST 2011
#1267: [raster] Add manual height/width support to ST_Resample
-----------------------------+----------------------------------------------
Reporter: serveralex | Owner: dustymugs
Type: enhancement | Status: reopened
Priority: medium | Milestone: PostGIS 2.0.0
Component: postgis raster | Version: trunk
Resolution: | Keywords: history
-----------------------------+----------------------------------------------
Changes (by bnordgren):
* status: closed => reopened
* resolution: fixed =>
Comment:
Replying to [comment:11 dustymugs]:
> Added support for width/height in r8153.
>
> The function signature changes are:
>
> ...
>
> width: the number of columns in the raster. width/height are
mutually exclusive to scalex/scaley
>
> height: the number of rows in the raster. width/height are mutually
exclusive to scalex/scaley
>
> ...
> usescale: if FALSE, the reference raster's width and height are used
instead of the X and Y scales.
>
Ok, I think what we need here is an explanation of how the un-
specified/ignored parameters are calculated. On top of that, we need a
justification for why these parameters are treated as mutually exclusive
when they are not. In particular, why are you disallowing the perfectly
legitimate case where the user provides a reference raster and wants you
to return something which is exactly on the same grid.
Optionally calculating missing parameters is a whole different ball game
than imposing an external criteria (relationship between width/height and
scalex/scaley) the user may not want.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1267#comment:12>
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