<div dir="ltr"><div dir="ltr">Thanks - sounds complicated.<div>I am running a fair bit of different stuff on the one remote server - including an install of QGIS and POSTGIS.<div>I might just spin up a tiny unique environment to get this job done, save messing up other things that rely on proj. </div></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br></div><div>Ben Boughton<div><br><br></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 23 Jun 2021 at 11:19, Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> On Wed, 23 Jun 2021 at 08:32, Ben Boughton <<a href="mailto:bboughton@gmail.com" target="_blank">bboughton@gmail.com</a>> wrote:<br>
> > Processing 1/1: testr.tif<br>
> > ERROR 1: PROJ: proj_as_wkt: SQLite error on SELECT name,<br>
> > ellipsoid_auth_name, ellipsoid_code, prime_meridian_auth_name,<br>
> > prime_meridian_code, area_of_use_auth_name, area_of_use_code,<br>
> > publication_date, deprecated FROM geodetic_datum WHERE auth_name = ?<br>
> > AND code = ?: no such column: area_of_use_auth_name<br>
> <br>
> You might have PROJ_LIB pointing to a different version of PROJ, as the<br>
schema<br>
> in proj.db has changed a few times between releases.<br>
> <br>
> <a href="https://proj.org/usage/environmentvars.html#envvar-PROJ_LIB" rel="noreferrer" target="_blank">https://proj.org/usage/environmentvars.html#envvar-PROJ_LIB</a><br>
> _______________________________________________<br>
> postgis-users mailing list<br>
> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br>
[Regina Obe] <br>
<br>
As Mike noted, proj.db has changed a number of times in proj releases.<br>
Last person I ran into with this particular problem was because they got<br>
their proj from main distro<br>
And they had installed QGIS/GDAL via UbuntuGIS which installed a newer<br>
version of proj. So they had two versions of proj, but the proj.db path was<br>
the newer.<br>
<br>
It was a mess to properly fix the install, so I ended up just giving him my<br>
copy of proj.db to overwrite his.<br>
<br>
Lesson: Don't mix distributions of GDAL/PROJ. Bad things happen.<br>
<br>
You can check which version of Proj your postgis is running with <br>
<br>
SELECT postgis_full_version();<br>
<br>
And whatever proj that says you should be using a proj.db that was built<br>
from that one.<br>
I've got a bunch of versions of proj hanging around, so I could give you my<br>
copy of proj.db for your version of Proj, if it comes to that.<br>
<br>
Hope that helps,<br>
Regina<br>
<br>
<br>
<br>
</blockquote></div>