I have a confession to make. I'm one of those folk who likes keeping my pictures in the database. File paths are just too annoying and when some network guy/gal decides to do some spring cleaning, all the pictures referenced in your database, associated with important projects are misplaced. On top of that paths aren't as easily accessible across firewall connections as database connections, vary depending on OS/network and are just ancient. I can go on and on about why I like my pictures in the database along side the data they pictorially describe, and some wise ass will tell me how wrong I am, so I'll stop here.

One thing I have always wanted to do is do all my cropping and resizing with the terseness and beauty that is SQL. With latest changes in PostGIS I can enjoy the same features with non-georeferenced pictures that I can with georeferenced ones. Thanks Bborie. We now have an ST_Resize function that doesn't require a known spatial reference system and many of the other gdal functions e.g. ST_ReSample have been changed in a similar fashion.

For these operations, I'm using:

POSTGIS="2.1.0SVN r10777" GEOS="3.4.0dev-CAPI-1.8.0 r0" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.9.1, released 2012/05/15" LIBXML="2.7.8" LIBJSON="UNKNOWN" RASTER

PostgreSQL 9.2.0, compiled by Visual C++ build 1600, 64-bit

Using the buildbot builds generated by Winnie PostGIS buildbot.