[postgis-devel] [PostGIS] #1336: [raster] Problem with ST_AsRaster() alignment

[PostGIS]

#1336: [raster] Problem with ST_AsRaster() alignment
----------------------------+-----------------------------------------------
 Reporter:  pracine         |       Owner:  pracine      
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by bnordgren):

 Checking consistency of alignment may well be something that the
 "physically relevant geotransform" code/algorithm could handle #1331 .
 (pixel sizes are always positive). You just need to make a determination
 as to whether "same alignment" includes the case where the j basis vectors
 are opposed by 180 degrees. For instance, is it more important to you that
 the transform be very simple like a shift and add, or is it just necessary
 to have the grid cells be co-located?

 In addition, it also becomes easier to circumscribe (''not'' inscribe)
 gdal's suggested extent with a raster definition if the physically
 significant parameters are available. Circumscribing an extent (GBOX) with
 the grid definition of a source raster is exactly what motivated #1331. I
 have an algorithm to circumscribe a gbox with a raster worked out on
 paper.

 This is actually the last known loose end for raster iterator.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1336#comment:6>
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.