id summary reporter owner description type status priority milestone component version resolution keywords cc 3148 Another GUC for PROJSO or can we just figure out the PROJSO? robe Bborie Park "So I started winnie's path to using proj 4.9.1 in prep for Windows 2.2 release with proj 4.9.1 (to take advantage of new geography goodness), and raster broke. {{{ passed Test: test_gdal_to_raster ...passed Test: test_gdal_warp ...ERROR 6: Unable to load PROJ.4 library (libproj-0.dll), creation of OGRCoordinateTransformation failed. Assertion failed! }}} proj 4.9.1 creates dll libproj-9.dll while the 4.8.0 series has libproj-0.dll I think before libproj-0.dll is the default unless I override it with something else. But now of course that default don't work with my 4.9.1 library. So {{{ SET PROJSO=libproj-9.dll }}} fixes the issue, but given I've got to ship to windows users who have every GIS thing under the sun, plus god knows what other versions of PostgreSQL/PostGIS running, I'd rather not muck with their system environment settings if I don't have to. It would be really nice if raster was smart enough to figure out which proj it was compiled with, but barring that, I guess I can maybe live with a GUC for PROJSO. " defect new medium PostGIS Fund Me raster master