[postgis-devel] [PostGIS] #1058: [raster] Two-raster spatial operations framework proposal

[PostGIS]

#1058: [raster] Two-raster spatial operations framework proposal
----------------------------+-----------------------------------------------
 Reporter:  bnordgren       |       Owner:  pracine      
     Type:  enhancement     |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by mcayland):

 Replying to [comment:8 bnordgren]:

 > I think I was unclear. Here's the situation:
 >
 > Liblwgeom depends on external libraries, such as geos. [OK]
 >
 > Raster depends on liblwgeom [OK]
 >
 > Raster also depends on postgis now [PROBLEM].
 >
 > It's the link between rtpostgis-2.0.so and postgis-2.0.so (with raster
 depending on postgis) which is problematic. In terms of your outline, this
 is the part which requires that problematic link:
 >
 > > 5) Rework postgis/lwgeom_transform.c cache code so it uses the
 underlying liblwgeom routines... and while you're there, also refactor it
 into a simple API so that adding caching to any other functions within
 PostGIS (as in linked with PostgreSQL) becomes much easier (and indeed, I
 believe you can test this by making the prepared geometry cache use your
 new code too).
 >
 > Do you see a way to avoid making this link?

 I think so? I was suggesting refactoring the reprojection code and moving
 its core into liblwgeom. Since raster already depends upon liblwgeom, then
 the problem is already solved and all other users of liblwgeom can also
 benefit from the revised functionality.

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