[postgis-devel] [PostGIS] #2123: ST_FromGDALRaster

[PostGIS]

#2123: ST_FromGDALRaster
-------------------------+--------------------------------------------------
 Reporter:  robe         |       Owner:  dustymugs     
     Type:  enhancement  |      Status:  new           
 Priority:  medium       |   Milestone:  PostGIS Future
Component:  raster       |     Version:  trunk         
 Keywords:               |  
-------------------------+--------------------------------------------------
 This I'm envisioning as a companion functions to ST_AsGDALRaster.

 http://www.postgis.org/documentation/manual-svn/RT_ST_AsGDALRaster.html

 It would take a bytea object and return a set of type raster.

 One specific use case.  I have this web service where people can upload
 drawings and other rasters like pictures and so forth.  Ideally I want to
 bring them in as postgis raster so I can use all the postgis plumbing to
 do things like extrude features, resize as needed and for some cases
 georeference based on associated objects in the database and so forth.

 I want it to return a set of raster rather than a single raster just
 because I may need it tiled in some cases and possibly because resulting
 size of a single might exceed our row limits.

 Format I'm thinking would be:

 {{{
 ST_FromGDALRaster(bytea gdal_rast, text[] options=NULL, integer
 srid=sameassource);
 }}}

 options would vary depending on raster type.  I'm assuming from the header
 of the gdal_rast blob we can infer the gdal type or have that passed in in
 the options arg? Or does this need to be passed in?  Not sure how
 raster2pgsql does it. I guess if it can never infer we would pass in as a
 separate arg.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2123>
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.