[postgis-devel] [PostGIS] #1141: [raster] ST_AsRaster

[PostGIS]

#1141: [raster]  ST_AsRaster
----------------------------+-----------------------------------------------
 Reporter:  dustymugs       |       Owner:  dustymugs    
     Type:  task            |      Status:  assigned     
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by pracine):

 For consistency of the API, I think it would be a good idea to develop a
 "parameter order" policy for all the functions that create, modify and
 return info on a raster georeference and all those that create, modify and
 return info on a band so that users get used to the order in which to
 provide the arguments. I also think that when both type of information
 must be provided or returned, all raster info should precede (or follow)
 band info.

 I think all the function below would greatly benefit from such a policy,
 but mostly future functions:

 Function needing/returning raster georeference info:

 -ST_MakeEmptyRaster()

 -ST_MetaData()

 -ST_SetGeoReference()

 Functions needing/returning bands info:

 -ST_AddBand()

 -ST_BandMetaData()

 Functions needing both:

 -ST_AsRaster()

 Could you write such a policy in the spec and apply it to every functions?
 Or at least just use it for future functions and create a ticket for past
 functions?

 That would be great. A shame I never did it...

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