<div dir="ltr"><div><div>you are right, if i dropped the aforementioned index, analyze works without issue. As long as I tried to create the index again, it does not let me creating the index but throw the same error.<br></div>But I wonder why it is working in the original database. What happened during the backup/restore that changed this?<br></div>Btw, I see some small difference in the output of the original database. May be it sounds something to you?<br><div><br></div><div>#This is the output from the original database<br></div>geodm=# SELECT postgis_full_version();<br><br> postgis_full_version<br><br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>---------------------------<br> POSTGIS="2.5.5" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.3.1" PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.1" LIBJSON="0.11" LIBPROT<br>OBUF="1.0.2" (core procs from "2.5.2 r17328" need upgrade) TOPOLOGY (topology procs from "2.5.2 r17328" need upgrade) RASTER (raster procs from "2.5.2 r17328" need upgrade) (sfcgal procs from "2<br>.5.2 r17328" need upgrade)<br>(1 row)<br><br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 27, 2023 at 10:21 PM Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</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">Could be your ST_Transform index triggering the issue and you have at least one geometry out of bounds in there.<br>
<br>
I’d try dropping your geobordervtc_geom_25832_idx and then rerunning analyze on the table.<br>
If that does fix it then try to gigure out which geometry is at fault.<br>
<br>
The 25632 is only good for utm zone 32N<br>
<br>
<a href="https://epsg.io/25832" rel="noreferrer" target="_blank">https://epsg.io/25832</a><br>
<br>
So I suspect you have a geometry way off from there causing the issue. <br>
<br>
Or it could be missing grid datum shift files at fault too.<br>
<br>
You can update your grid files by running at your command line:<br>
<br>
projsync --all<br>
<br>
As detailed here - <a href="https://proj.org/apps/projsync.html#index-0" rel="noreferrer" target="_blank">https://proj.org/apps/projsync.html#index-0</a><br>
<br>
--------------------------------------<br>
<br>
From: postgis-users [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>] On Behalf Of pham lan<br>
Sent: Monday, March 27, 2023 4:02 PM<br>
To: PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
Subject: Re: [postgis-users] ERROR: transform: Point outside of projection domain (2050)<br>
<br>
Hi Regina,<br>
Here are more information:<br>
<br>
geodm=# SELECT postgis_full_version();<br>
postgis_full_version<br>
<br>
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
----------------<br>
POSTGIS="2.5.5" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0"<br>
TOPOLOGY RASTER<br>
(1 row)<br>
<br>
<br>
<br>
On Mon, Mar 27, 2023 at 9:43 PM Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>> wrote:<br>
What’s the structure of the table in question?<br>
<br>
\d+ name_of_table<br>
<br>
Should give needed details.<br>
<br>
Also output of <br>
<br>
SELECT postgis_full_version();<br>
<br>
From: postgis-users [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>] On Behalf Of pham lan<br>
Sent: Monday, March 27, 2023 3:27 PM<br>
To: PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
Subject: [postgis-users] ERROR: transform: Point outside of projection domain (2050)<br>
<br>
Hi everyone,<br>
<br>
I need your help to figure this out. I have a DB in postgresql 10 with postgis 2.5. I know postgresql 10 is not supported anymore and we have plan to upgrade it soon but it is a different story.<br>
The thing is, I want to make a copy of this DB, so I tried a pg_basebackup to another postgres10+postgis 2.5 VM. After that, a vacuum went well but the analyzer throws an error on 1 specific table:<br>
ERROR: transform: Point outside of projection domain (2050)<br>
i tried also pg_dump/pg_restore but get the same error. Does anyone know what is the problem?<br>
<br>
Thanks for your help!<br>
Regards,<br>
Lan<br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br>
<br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br>
</blockquote></div>