srtext 2048 length limit

[Denis Rykov]

Thank you, Paul and Regina, for the prompt response.

I don't have a specific example at hand right now, but from what I
observed, the issue seems to arise when the WKT is in a 'prettified' format
where elements are indented with extra spaces for readability. If those
extra spaces are removed, the WKT would likely fit within the 2048 limit.
However, it would be helpful to have a way to store it as-is, without
needing to strip the formatting.

On Wed, May 21, 2025, 4:59 PM Paul Ramsey <pramsey at cleverelephant.ca> wrote:

>
>
> > On May 21, 2025, at 7:43 AM, Regina Obe <lr at pcorp.us> wrote:
> >
> > The general advice is if you want to make changes, you should make it in
> your proj.db database since that is the first source of truth for PostGIS
> these days.
> >
>
> Er, not really. If you want to change an INSTALLED srs, then you kind of
> have to do it in proj.db, since that’s the first place we check when
> dereferencing an SRID number. If you want to ADD a new srs, you can add a
> line to spatial_ref_sys. Frankly, even if you wanted to change an existing
> srs, the smart thing to do would be to add a new line and a new srid number
> to spatial_ref_sys, because there’s nothing stopping proj.db from being
> over-written by software upgrades etc.
>
> P
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20250521/5c510bd3/attachment.htm>