RE: pgr_alphashape is returning a geometry collection?

I think this is correct, your query statement is 'SELECT pgr_alphaShape((st_collect(v.the_geom))) as geom FROM ways_vertices_pgr as v, result as r WHERE r.node = v.id;'. The return value of the pgr_alphaShape function is a GEOMETRY COLLECTION. For reference, please seehttps://

Re: pgr_alphashape is returning a geometry collection?

The function pgr_alphashape returns "GEOMETRY COLLECTION" as its result. For reference, please see https://docs.pgrouting.org/3.6/en/pgr_alphaShape.html. In PostGIS, the function used is ST_AlphaShape, which returns a geometry. An alpha-shape is a (usually) concave polygonal geometry that

ST_Slope query is slow.

Hello, -The computation of slope (in degrees) is relatively slow, taking about 20 seconds for analysis using ArcGIS Pro. version:pg12+postgis340 --postgis_full_version POSTGIS="3.4.0 0" [EXTENSION] PGSQL="120" GEOS="3.12.0-CAPI-1.18.0" SFCGAL="SFCGAL 1.4.1, CGAL 5.4.5, BOOST 1.72.0" PRO

Re: The intersect function does not utilize indexes

mentioned error message. Regina Obe 于2024年2月23日周五 10:23写道： > You have an example query where you are seeing this behavior? > > > > *From:* Dapeng Wang > *Sent:* Thursday, February 22, 2024 8:57 PM > *To:* PostGIS Users Discussion > *Subject:* The intersect function does

The intersect function does not utilize indexes

Hello everyone, I have a client with a database developed on PostgreSQL 12, with both Windows and Linux versions. Everything is normal with the Linux version, but there are anomalies with the Windows version. While the Windows database can have the PostGIS extension installed, create indexes,

Re: The intersect function does not utilize indexes

gher version number on your windows system than your > Linux. > > > > Also make sure > > > > SELECT postgis_full_version(); > > > > Doesn’t say you need updates. If it does make sure to run > > > > SELECT postgis_extensions_upgrade(); > > >

Re: The intersect function does not utilize indexes

t; > The other place I’ve see that kind of issue is with foreign tables, but I > assume you are not using any of those. > > > > *From:* Dapeng Wang > *Sent:* Sunday, February 25, 2024 9:09 AM > *To:* Regina Obe > *Cc:* PostGIS Users Discussion > *Subject:* Re: The inte

Re: The intersect function does not utilize indexes

that’s what my focus has been on > right now and once I have that working, I’ll have build instructions for > that. But I’ve still got a ways to go. > > > > Thanks, > > Regina > > > > > > > > *From:* Dapeng Wang > *Sent:* Tuesday, February 27, 2024 1:

[postgis-users] Sample SQL statement showing error

Hello everyone, https://postgis.net/docs/manual-dev/RT_ST_Clip.html https://postgis.net/docs/manual-dev/zh_Hans/RT_ST_Clip.html The sample sql statements in English and Chinese are displayed differently. Examples: Comparing selecting all touched vs. not all touched. One is "=>", the other is "=

[postgis-users] Operator does not exist: <<#>>

Hello everyone, SELECT st_distance(geom, 'SRID=4326;POINT(1 2)'::geometry) FROM ne_110m_admin_0_countries ORDER BY (ST_GeomFromText('POINT(1 2)') <<#>> geom) operator does not exist: geometry <<#>> geometry Reference https://postgis.net/docs/manual-dev/en/geometry_distance_box_nd.html Checked

Re: [postgis-users] Operator does not exist: <<#>>

I get it, <<#>> is deprecated. <<->>Supports 2D and 3D operations, shortest distance. I also verified via SQL that <<->> is indeed the shortest distance. There are 2 questions here, 1. The centroid algorithm disappears. 2. How to calculate bounding box distance used in 3D? Initially use <<#>>.