pg.ddx.io  postgis-users@lists.osgeo.org mailing list archive (PostGIS users)  
help / color / mirror / Atom feed
longer EPSG WKT2
2+ messages / 2 participants
[nested] [flat]

* longer EPSG WKT2
@ 2026-09-09 14:16 Greg Troxel <gdt@lexort.com>
  2026-09-09 14:42 ` longer EPSG WKT2 Regina Obe <lr@pcorp.us>
  0 siblings, 1 reply; 2+ messages in thread

From: Greg Troxel @ 2026-09-09 14:16 UTC (permalink / raw)

EPSG now has an ensemble for ETRS89 and those have many members, e.g.

  https://epsg.org/crs/wkt/id/25830

which are well beyond the 2048 size in the table definition.

I therefore wonder:

  What version of the EPSG database does postgis come with (seems hard
  to find in NEWS?)?

  What is the relationship between the postgis EPSG version and the proj
  EPSG version?

  Should the table fields become larger?  Perhaps 16384?

and

  If postgis depends on proj, why isn't it just using the EPSG database
  from proj?


(This issue was raised by Javier on the proj list.)



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* longer EPSG WKT2
  2026-09-09 14:16 longer EPSG WKT2 Greg Troxel <gdt@lexort.com>
@ 2026-09-09 14:42 ` Regina Obe <lr@pcorp.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Regina Obe @ 2026-09-09 14:42 UTC (permalink / raw)

> EPSG now has an ensemble for ETRS89 and those have many members, e.g.
> 
>   https://epsg.org/crs/wkt/id/25830
> 
> which are well beyond the 2048 size in the table definition.
> 
> I therefore wonder:
> 
>   What version of the EPSG database does postgis come with (seems hard
>   to find in NEWS?)?
> 
>   What is the relationship between the postgis EPSG version and the proj
>   EPSG version?
> 
>   Should the table fields become larger?  Perhaps 16384?
> 
> and
> 
>   If postgis depends on proj, why isn't it just using the EPSG database
>   from proj?
> 
> 
> (This issue was raised by Javier on the proj list.)

It is mostly just using the proj.db.  Anything beyond storage of srid and
auth_srid is considered legacy use in PostGIS.
PostGIS always checks proj.db for core definitions if the auth_srid exists
in the proj.db. The srtext / proj4text is only used of the definitions don't
exist in proj.db.

We've had this debate for a while if PostGIS should just come with an
essentially empty spatial_ref_sys and as part of user responsibility load
what they need to load
from proj.db and even making spatial_ref_sys a view that just wraps a
function that reads from proj.db. That would largely solve the issue with
have with pg_upgrade that in some cases tables are loaded before
spatial_ref_sys is populated.

There was discussion that editing the proj.db is harder to edit than the
spatial_ref_sys for users wanting to define their own custom projection, so
that was the big boo against getting rid of spatial_ref_sys as a table.
Other reason is it would probably kill performance.






^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2026-09-09 14:42 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-09-09 14:16 longer EPSG WKT2 Greg Troxel <gdt@lexort.com>
2026-09-09 14:42 ` Regina Obe <lr@pcorp.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox