[postgis-tickets] [PostGIS] #5024: spatial_ref_sys table not updated with new entries

[PostGIS]

#5024: spatial_ref_sys table not updated with new entries
----------------------+---------------------------
  Reporter:  robe     |      Owner:  strk
      Type:  defect   |     Status:  reopened
  Priority:  medium   |  Milestone:  PostGIS 3.3.0
 Component:  postgis  |    Version:  3.1.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 Replying to [comment:22 pramsey]:
 > It seems to me that a far simpler and easier to reason about change
 would be to convert spatial_ref_sys.sql into a CSV file and have two build
 targets, one for spatial_ref_sys_create.sql that gets bundled into the
 CREATE EXTENSION script and one for spatial_ref_sys_update.sql that
 consists up upserts and gets bundled into the ALTER EXTENSION UPDATE
 script.
 >

 pramsey how about this -- you put in your code and backport it to 3.2
 since your code is backward compatible. Make sure you have tests please.

 I still don't like your solution though.  This whole keep in X range of
 SRIDs I've always found difficult to stomach especially when I'm getting
 SRIDs from other sources and we've never clearly stated that requirement.

 > People always have the latest entries per the amazon email, and the
 situation is very simple and easily documented: create your custom entries
 out of the way of EPSG (<32600) and out of the way of ESRI. The table
 remains very simple and the logic is very easy to explain.

 What amazon email?


 >
 > I think the latter point (simplicity of impact) is underappreciated WRT
 the proposed view, as even I, a lover of spatial reference systems, feel
 my eyes glaze over as proponents talk about the various cases and possible
 flags and intermediate states of "systems in both tables with a warning in
 the script".

 I'm more annoyed I can't easily distinguish my entries from system
 distributed ones.
 So you are right I'm under appreciating this simplicity.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5024#comment:23>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.