<div dir="ltr"><div>PROJCS is WKT1. In WKT2 it would be PROJCRS (note the R)</div><div><br></div><div>As far as I understood, PostGIS does now support WKT2 (but maybe I am wrong)</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, 9 Sept 2026 at 16:09, Greg Troxel via PROJ <<a href="mailto:proj@lists.osgeo.org">proj@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Javier Jimenez Shaw via PROJ <<a href="mailto:proj@lists.osgeo.org" target="_blank">proj@lists.osgeo.org</a>> writes:<br>
<br>
> In the new PROJ release 9.9.0 that will be released soon, the latest<br>
> version of EPSG is included.<br>
> As I already mentioned, all European realizations are included in the WKT2<br>
> of any CRS using the ETRS89 datum ensemble.<br>
> This is an example of EPSG:25830, with 4264 chars.<br>
> <a href="https://epsg.org/crs/wkt/id/25830" rel="noreferrer" target="_blank">https://epsg.org/crs/wkt/id/25830</a><br>
> If you format it a bit nicely it goes up to 4874. And this is just an<br>
> example.<br>
><br>
> I realized today that in PostGIS the table containing the CRS has fields<br>
> limited to 2048 chars, in particular "srtext".<br>
> <a href="https://postgis.net/docs/using_postgis_dbmanagement.html#spatial_ref_sys_table" rel="noreferrer" target="_blank">https://postgis.net/docs/using_postgis_dbmanagement.html#spatial_ref_sys_table</a><br>
><br>
> CREATE TABLE spatial_ref_sys (<br>
>   srid       INTEGER NOT NULL PRIMARY KEY,<br>
>   auth_name  VARCHAR(256),<br>
>   auth_srid  INTEGER,<br>
>   srtext     VARCHAR(2048),<br>
>   proj4text  VARCHAR(2048)<br>
> )<br>
<br>
I have locally installed 9.9.0RC1 (and proj-data 1.25RC1, surely<br>
unrelated), and built postgis.<br>
<br>
Looking at spatial_ref_sys.sql, I see<br>
<br>
--                                                                                                                                                                                                                                             <br>
-- EPSG 25830 : ETRS89 / UTM zone 30N                                                                                                                                                                                                          <br>
--                                                                                                                                                                                                                                             <br>
(25830, 'EPSG', 25830, 'PROJCS["ETRS89 / UTM zone 30N",GEOGCS["ETRS89",DATUM["European_Terrestrial_Reference_System_1989",SPHEROID["GRS 1980",6378137,298.257222101,AUTHORITY["EPSG","7019"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6258"]]\<br>
,PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4258"]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",-3],PARA\<br>
METER["scale_factor",0.9996],PARAMETER["false_easting",500000],PARAMETER["false_northing",0],UNIT["metre",1,AUTHORITY["EPSG","9001"]],AXIS["Easting",EAST],AXIS["Northing",NORTH],AUTHORITY["EPSG","25830"]]', '+proj=utm +zone=30 +ellps=GRS8\<br>
0 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs '),<br>
<br>
which appears not to include the ensemble members.  I don't see a<br>
postgis NEWS about a new EPSG version since 2.5.0, but obviously that<br>
isn't how it is.<br>
_______________________________________________<br>
PROJ mailing list<br>
<a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/proj" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/proj</a><br>
</blockquote></div>