[postgis-devel] PSC Vote: Proposal: drop support for libproj < 6.1 in PostGIS 3.3.0

[Regina Obe]

+1 for dropping Proj < 6.1 in PostGIS 3.3.0

> PROs:
>   - we could query the proj db for spatial_ref_sys entries
>     ( https://trac.osgeo.org/postgis/ticket/5094 )
>     and stop shipping spatial_ref_sys.sql all togheter
>     (as suggested by Raul)
>   - we could drop a few #idefs
> 
[Regina Obe] 
Are we still here with the plan of having as we discussed in IRC  a function
that runs during create extension / ALTER EXTENSION

That queries the proj.db to pull entries for insert into spatial_ref_sys?
And exposable so that a user can call it anytime to update existing entries
/ insert new entries?


> CONs:
>   - people running in production older proj won't be able
>     to upgrade ONLY postgis w/out upgrading libproj
>     (meh)
> 
[Regina Obe] 
I suspect this is not a huge problem as a newer PostGIS often is shipped
with a newer Proj.


> Thanks Regina we now have libproj support matrix written
> here: https://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS
> The table puts proj 6.0-6.3 togheter, not sure why, our code seems to want
> 6.1+ for some specific things.
[Regina Obe] 
I've broken 6.0 out.  I think our ifdefs around there were because 6.0 was
very buggy.
I think 6.1 might have been too.

Also as mentioned, my breakout of Proj and Update of GDAL is strictly from
memory.
Need to revisit the postgis code to make sure my assumptions are right

Like I think 5.2 might need to be in a separate bucket.  Can't remember
where geographicLib came into the mix.