[postgis-users] ERROR: transform: Point outside of projection domain (2050)
pham lan
phamlankt at gmail.com
Sun Apr 2 23:54:13 PDT 2023
In my case, proj72 and proj82 come as dependencies of postgis25_10 and as I
can see, those both are also dependencies of the postgis25_12 package.
On Mon, Apr 3, 2023 at 5:31 AM Regina Obe <lr at pcorp.us> wrote:
> I’m thinking maybe the crashing issues you are running into are this bug.
>
>
>
> https://redmine.postgresql.org/issues/6528
> “Mixed proj72 and proj80 dependencies causing crashes again”
>
>
>
> As far as where the proj share is installed, not sure off hand. I presume
> it would be custom path but not sure where that is set.
>
>
>
> When you do
>
>
>
> yum search proj72
>
>
>
>
>
> Do you get an output that proj 7.2.1 is installed. I’m wondering if maybe
> you can just uninstall proj72
>
>
>
> Might help to report issue on pgsql-pkg-yum mailing list
> https://www.postgresql.org/list/pgsql-pkg-yum/ as this sounds like a
> packaging issue.
>
>
>
> Hope that helps,
>
> Regina
>
>
>
>
>
>
>
>
>
> *From:* postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] *On
> Behalf Of *pham lan
> *Sent:* Tuesday, March 28, 2023 10:15 PM
> *To:* PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> *Subject:* Re: [postgis-users] ERROR: transform: Point outside of
> projection domain (2050)
>
>
>
> Thanks,
>
> I ran the command and it downloaded all files into
> /root/.local/share/proj/. I ran the Analyze command again and got the same
> error.
>
> Do I need to copy these downloaded files to a special path in order for
> postgis to take it?
>
>
>
> On Tue, Mar 28, 2023 at 10:55 PM Regina Obe <lr at pcorp.us> wrote:
>
> I thought I had mentioned running projsync, but maybe I sent before I
> added that note.
>
>
>
> Try running at the command line:
>
>
>
> projsync --all
>
>
>
> As detailed in :
>
>
>
> https://proj.org/apps/projsync.html#index-0
>
>
>
>
>
> *From:* postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] *On
> Behalf Of *pham lan
> *Sent:* Tuesday, March 28, 2023 2:34 PM
> *To:* PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> *Subject:* Re: [postgis-users] ERROR: transform: Point outside of
> projection domain (2050)
>
>
>
> Hi Regina,
>
> I did a pg_basebackup from Postgresql10(with postgis2.5) to postgresql10
> (with postgis2.5) and the vacuum command went well.
> * /usr/pgsql-10/bin/vacuumdb -p 5433 --db geodm --analyze-in-stages
> --verbose*
>
> When I did upgrade postgis 2.5 to 3.0, the upgrade went ok but the vacuum
> analyze gave the same error. If it is the PROJ version different which
> causes this problem, what is the good way to deal with this
>
>
> *INFO: "geobordervtx": scanned 2665 of 2665 pages, containing 106839 live
> rows and 0 dead rows; 3000 rows in sample, 106839 estimated total
> rowsvacuumdb: vacuuming of database "geodm" failed: ERROR: transform:
> Point outside of projection domain (2050)*
>
>
>
> #This is the output from the database before postgis upgrade
>
> geodm=# SELECT postgis_full_version();
>
> postgis_full_version
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ---------------------------
> 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
> 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
> .5.2 r17328" need upgrade)
>
>
>
>
>
> #This is the output from the database after postgis upgrade
>
>
>
>
>
>
>
> *geodm=# SELECT postgis_full_version();
>
> postgis_full_version------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ POSTGIS="3.0.7
> 487b488" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.4.1"
> PROJ="8.2.1" GDAL="GDAL 3.3.3, released 2021/10/25" LIBXML="2.9.7"
> LIBJSON="0.13.1" LIBPROTOBUF="1.3.0" WAGYU="0.4.3 (Internal)" TOPOLOGY
> RASTER*
>
>
>
> On Mon, Mar 27, 2023 at 11:53 PM Regina Obe <lr at pcorp.us> wrote:
>
> Did you run
>
>
>
> SELECT postgis_extensions_upgrade();
>
> SELECT postgis_extensions_upgrade();
>
>
>
>
>
> Twice on your 3.0?
>
>
>
> You should actually do the same on your 2.5 as well, as they are both at
> unstable states. The PostGIS 3.0 more so is unstable, cause it looks to
> have a mix of using the 2.5 and 3.0 libraries.
>
>
>
> I don’t think the 2.5 even supported Proj 8.2 or at least not a
> combination we’ve tested.
>
>
>
> Probably the issue is with difference in Proj 7.2 vs Proj 8.2.1
>
>
>
> Do you have these running on the same server or different servers?
>
>
>
> I think the proj.db files changed between 7.2 and 8.2 and so if the 8.2 is
> using a proj.db from 7.2 that could be a mess.
>
>
>
>
>
>
>
> *From:* postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] *On
> Behalf Of *pham lan
> *Sent:* Monday, March 27, 2023 4:59 PM
> *To:* PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> *Subject:* Re: [postgis-users] ERROR: transform: Point outside of
> projection domain (2050)
>
>
>
> Sorry, my bad. I just realized that the information about the postgis
> version I gave you was wrong. So the original one is 2.5 and the backup one
> is 3.0. Can it be that the st_transform function caused the problem in this
> case for different postgis functions?
>
> So the output of select postgis_full_version() are following:
>
> #This is the output from the original database
>
> geodm=# SELECT postgis_full_version();
>
> postgis_full_version
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ---------------------------
> 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
> 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
> .5.2 r17328" need upgrade)
>
> #This is output of the target database:
> geodm=# select postgis_full_version();
>
> postgis_full_version
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> --------------------------------------------------------
> POSTGIS="3.0.7 r487b488" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3"
> SFCGAL="1.4.1" PROJ="8.2.1" GDAL="GDAL 3.2.3, released 2021/04/27"
> LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0"
> (core procs from "2.5.2 r17328" need upgrade) TOPOLOGY (topology procs
> from "2.5.2 r17328" need upgrade) RASTER (raster lib from "2.5.5 r0" need
> upgrade) (raster procs from "2.5.2 r17328" need u
> pgrade) (sfcgal procs from "2.5.2 r17328" need upgrade)
>
>
>
>
>
> On Mon, Mar 27, 2023 at 10:41 PM pham lan <phamlankt at gmail.com> wrote:
>
> 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.
>
> But I wonder why it is working in the original database. What happened
> during the backup/restore that changed this?
>
> Btw, I see some small difference in the output of the original database.
> May be it sounds something to you?
>
>
>
> #This is the output from the original database
>
> geodm=# SELECT postgis_full_version();
>
> postgis_full_version
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ---------------------------
> 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
> 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
> .5.2 r17328" need upgrade)
> (1 row)
>
>
>
> On Mon, Mar 27, 2023 at 10:21 PM Regina Obe <lr at pcorp.us> wrote:
>
> Could be your ST_Transform index triggering the issue and you have at
> least one geometry out of bounds in there.
>
> I’d try dropping your geobordervtc_geom_25832_idx and then rerunning
> analyze on the table.
> If that does fix it then try to gigure out which geometry is at fault.
>
> The 25632 is only good for utm zone 32N
>
> https://epsg.io/25832
>
> So I suspect you have a geometry way off from there causing the issue.
>
> Or it could be missing grid datum shift files at fault too.
>
> You can update your grid files by running at your command line:
>
> projsync --all
>
> As detailed here - https://proj.org/apps/projsync.html#index-0
>
> --------------------------------------
>
> From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On
> Behalf Of pham lan
> Sent: Monday, March 27, 2023 4:02 PM
> To: PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> Subject: Re: [postgis-users] ERROR: transform: Point outside of projection
> domain (2050)
>
> Hi Regina,
> Here are more information:
>
> geodm=# SELECT postgis_full_version();
>
> postgis_full_version
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ----------------
> 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"
> TOPOLOGY RASTER
> (1 row)
>
>
>
> On Mon, Mar 27, 2023 at 9:43 PM Regina Obe <lr at pcorp.us> wrote:
> What’s the structure of the table in question?
>
> \d+ name_of_table
>
> Should give needed details.
>
> Also output of
>
> SELECT postgis_full_version();
>
> From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On
> Behalf Of pham lan
> Sent: Monday, March 27, 2023 3:27 PM
> To: PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> Subject: [postgis-users] ERROR: transform: Point outside of projection
> domain (2050)
>
> Hi everyone,
>
> 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.
> 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:
> ERROR: transform: Point outside of projection domain (2050)
> i tried also pg_dump/pg_restore but get the same error. Does anyone know
> what is the problem?
>
> Thanks for your help!
> Regards,
> Lan
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230403/6ca62f23/attachment.htm>
More information about the postgis-users
mailing list