You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SELECT ST_Covers(a1, a2)
FROM ST_GeomFromText('MULTIPOLYGON(((1 0,0 1,-1 0,0 -1, 1 0)))')
As a1,
ST_GeomFromText('MULTIPOINT(EMPTY,(0 0)) ')
As a2;
-- actual{f}, expected{t}
According to the definition of ST_Cover below and the point of geometry a2 lies inside, geometry a1 covers a2.
Returns true if every point in Geometry/Geography B lies inside
But Postgis doesn't consider the cover relationship which seems a bug.
Version is the latest from GitHub:
POSTGIS="3.5.0dev 3.4.0rc1-749-g42f04a29e" [EXTENSION] PGSQL="170" GEOS="3.13.0dev-CAPI-1.18.0" PROJ="8.2.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db" LIBXML="2.9.13" (core procs from "3.5.0dev 3.4.0rc1-748-gaedf3b14f" need upgrade)
The text was updated successfully, but these errors were encountered:
It could be an optimization issue. In the compile process, there is a file named configure. ST_Cover returns the expected result True if I add --enable-debug option to execute it. However, ST_Cover returns the unexpected result False when I remove --enable-debug :
Consider the following statement:
According to the definition of ST_Cover below and the point of geometry a2 lies inside, geometry a1 covers a2.
But Postgis doesn't consider the cover relationship which seems a bug.
Version is the latest from GitHub:
POSTGIS="3.5.0dev 3.4.0rc1-749-g42f04a29e" [EXTENSION] PGSQL="170" GEOS="3.13.0dev-CAPI-1.18.0" PROJ="8.2.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db" LIBXML="2.9.13" (core procs from "3.5.0dev 3.4.0rc1-748-gaedf3b14f" need upgrade)
The text was updated successfully, but these errors were encountered: