[postgis-tickets] [PostGIS] #2247: [raster] Create ST_CreateOverviews()

[PostGIS]

#2247: [raster] Create ST_CreateOverviews()
-------------------------------+--------------------------------------------
 Reporter:  dzwarg             |       Owner:  strk         
     Type:  enhancement        |      Status:  assigned     
 Priority:  medium             |   Milestone:  PostGIS 2.2.0
Component:  raster             |     Version:  trunk        
 Keywords:  raster, overviews  |  
-------------------------------+--------------------------------------------

Comment(by pracine):

 About the parameters names:

 -"ext" should be named "extent"
 -"sfx" and "sfy" should be named "scalex" and "scaley" like other raster
 functions
 -"tw" and "t"h should be named "tilewidth" and "tileheight"

 In general I prefer long self explaining parameter's names so sometimes I
 just have to look at the signature to understand what is what.

 What is the advantage of having a "regclass" parameter over a "name"
 parameter for the table and schema names like in AddRasterConstraints()
 and DropRasterConstraints() and others? I personnally have to search
 further in the doc to know how to specify this "regclass" argument.
 Annoying...

 A general revision of parameter names would be welcome. This is essential
 for easier use of the API. For example, we now have four different ways to
 refer to schema, table and column names:

 name rasttable, name rastcolumn (AddRasterConstraints,
 DropRasterConstraints, )
 name schema_name, name table_name, name column_name (UpdateRasterSRID)
 regclass tab, name col (ST_Retile)
 text rastertable, text rastercolumn (ST_Histogram, ST_SummaryStats,
 ST_ValueCount)

 Two different names for algorithm ("algorithm" and "algo").

 Four different names for band numbers ("band", "nband", "bandnum" and
 "band_num")

 Sometimes we name long arguments using underscores
 ("exclude_nodata_value") and sometimes we don't ("padwithnodata").

 If we don't want to change that many signatures, we migth at least not
 introduce new ones...

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2247#comment:29>
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.