[postgis-devel] PSC Vote: Make spatial_ref_sys as a view

[Regina Obe]

I think that might be a solution if we decided to have a function that reads from proj library as Raul was suggesting.

I’m not sure how long that would take to refresh though if it is only done during upgrade / install.

The time might be too prohibitive for an install though.

 

In that model – spatial_ref_sys_postgis would be swapped out with a function that peaks into proj.db but the spatial_ref_sys_user table would still remain.

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Bruce Rindahl
Sent: Tuesday, February 8, 2022 1:49 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PSC Vote: Make spatial_ref_sys as a view

 

Trivial comment.  If this is implemented it could be a materialized view for speed as it will be rarely updated.

 

On Tue, Feb 8, 2022 at 9:58 AM Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> > wrote:

> Anyways, I'm a -0 shading into a negative one unless you trot out some
users
> who will worship this change.
> 
> P.
> 
[Regina Obe] 
Paul,

If you do decide to give a -1 for this, please come up with an alternative
plan for fixing this bug moving forward
and making sure it stays fixed.

My feeling is spatial projections are more influx these days, so this will
become more of an issue moving forward.

https://trac.osgeo.org/postgis/ticket/5024

What I liked about strk's solution is that it provides a clear audit trail
of

1) Is the user's entries they are complaining about different from what we
published.
2) Have we changed entries from one upgrade to another.
3) It lets the user know they have entries different from what we shipped by
checking 
and a path for a user to ignore or purge their custom ones to be inline.  

SELECT postgis_full_version();

4) It provides a path forward to what Darafei and Raul have been complaining
about that spatial_ref_sys table is not a flexible enough way of dealing
with this.

5) In some cases if a user is using old entries and indexes based on that,
they might not want to use the "more correct ones" as it screws up there
workflow.
I have some clients that fit into that boat.

Thanks,
Regina






_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20220208/bf675cbb/attachment-0001.html>