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

[Regina Obe]

> > On Feb 11, 2022, at 4:06 PM, Regina Obe <lr at pcorp.us> wrote:
> >
> > 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?
> 
> You need to do some API archaeology on proj to see at what version the API
> is rich enough to generate full srs table data.
> 
> Meanwhile, that's not something that should be bound up with this
> discussion, which is really about what kind of platform support we can
> expect for a proj > 6 requirement.
> 
> P.
[Regina Obe] 
Separate topic  though it's one of the main reasons to drop older proj.

As strk noted below in his PROs.  So if that is not achievable with say 6.3
or above
I'm not sure it's worth the trouble to drop for savings of a few ifdefs 
aside from giving all users a more similar experience

---- strk's listed PROs
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 together
    (as suggested by Raul)
  - we could drop a few #idefs

@Even,

If you are not fed up with us already, you know off hand which version of
PROJ would make the above
feasible?

I think we all got excited with your benchmark of 1.6 seconds to pull all
the spatial_ref_sys from master proj.db

https://lists.osgeo.org/pipermail/postgis-devel/2022-February/029463.html


Thanks,
Regina