[postgis-tickets] [PostGIS] #5024: spatial_ref_sys table not updated with new entries
PostGIS
trac at osgeo.org
Wed Feb 9 01:40:06 PST 2022
#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 strk):
What I'm not sure about is whether we can REALLY clearly document and
stick to SRID ranges, which is what you're basically saying with:
> out of the way of EPSG (<32600) and out of the way of ESRI
This is my current set of max srids per auth_name:
{{{
strk=# select max(srid), auth_name from spatial_ref_sys group by
auth_name;
max | auth_name
--------+------------------------
900913 | spatialreferencing.org
32766 | EPSG
104992 | ESRI
(3 rows)
}}}
In my 2012 mail I tried to discuss this but nobody followed up:
https://lists.osgeo.org/pipermail/postgis-devel/2012-February/018440.html
Sticking with a fixed system range means simplifying the pg_extension
record as to what needs to be dumped from spatial_ref_sys. It still
doesn't save "tweaks to system SRIDs" but so far I think nobody came up
with that use case.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5024#comment:27>
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.
More information about the postgis-tickets
mailing list