[postgis-devel] [PostGIS] #925: [raster] ST_Transform

[PostGIS]

#925: [raster] ST_Transform
----------------------------+-----------------------------------------------
 Reporter:  dustymugs       |       Owner:  pracine              
     Type:  task            |      Status:  new                  
 Priority:  medium          |   Milestone:  PostGIS Raster Future
Component:  postgis raster  |     Version:  trunk                
 Keywords:                  |  
----------------------------+-----------------------------------------------
 This function would provide rasters the ability to do on-the-fly
 reprojections.  It may be possible that underlying code could be shared
 with the planned ST_Warp and ST_Resample functions but for now, the code
 will focus on supporting ST_Transform.

 A significant limitation with the C warp API in GDAL is that it is a
 subset of the C++ API.  Based upon my review of the C warp functions
 available and the code for
 [https://svn.osgeo.org/gdal/trunk/gdal/apps/gdalwarpsimple.c
 gdalwarpsimple.c], it looks like we are severely constrained by the
 function GDALSimpleImageWarp.  According to the docs,
 GDALSimpleImageWarp's "algorithm is called simple because it lacks many
 options such as resampling kernels (other than nearest neighbour), support
 for data types other than 8bit, and the ability to warp images without
 holding the entire source and destination image in memory."

 So, my question is, do we go C++, put ST_Transform on the backburner while
 the C API is improved or do what we can with the current C API?

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