Running clustering queries
Regina Obe
lr at pcorp.us
Wed May 8 14:53:48 PDT 2024
> > Which I can't find in our spatial_ref_sys table (guess our table needs
> > an update), but you can add with the below as long as you are using
> > PostGIS 2.5 or higher and PROJ 7 or higher, it's going to relegate all the
> details to PROJ anyway So the other columns will not be needed except these
> 3.
> >
> > INSERT INTO spatial_ref_sys(srid, auth_name, auth_srid) VALUES(9311,
> > 'EPSG', 9311);
> >
> >
> > But anyway either should work I think with 2163 there was some issue
> > with one of the proj settings which wouldn't impact your measurement but
> would affect proper display.
>
> I stumbled into this issue today. The lack of 9311 in spatial_ref_sys. Is a fix
> for this coming or is the spatial_ref_sys just known to be stale and not getting
> updated with updated postgis releases?
>
> thanks
> daryl
Daryl we've been discussing this forever. We used to go thru a yearly process or so of updating this list (at least for the next minor release).
Since we introduced https://postgis.net/docs/manual-3.4/postgis_srs_all.html or https://postgis.net/docs/manual-3.4/postgis_srs_search.html you can pull this yourself and populate your spatial_ref_sys with whatever you feel is missing.
Paul and Sandro,
Any thoughts on this. I know we went back and forth with "Why don't we just populate spatial_ref_sys using postgis_srs_all or some other such thing or why don't we just change spatial_ref_sys to a view that relegates to reading these from proj.db make spatial_ref_sys a view or why don't we make it a reduced set.
Not sure where we landed on that discussion.
Before the issue was because we supported such old proj versions, but now our minimum for 3.5 is 6.1 so all the options we had are now doable with our minimum proj version.
More information about the postgis-users
mailing list