Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-35764

ST_OVERLAPS returns true despite dim(intersection) ≠ dim(original input)

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5, 10.6, 10.11, 11.4
    • 10.6, 10.11, 11.4
    • GIS
    • None

    Description

      DROP table if EXISTS t1;
      DROP table if EXISTS t2;
      CREATE TABLE t1(geom geometry NOT NULL);
      CREATE TABLE t2(geom geometry NOT NULL);
      INSERT INTO t1 (geom) VALUES(ST_GeomFromText('POLYGON ((0 0, 0 1, 1 1, 1 0, 0 0))'));
      INSERT INTO t2 (geom) VALUES(ST_GeomFromText('POLYGON ((1 1, 1 2, 2 2, 2 1, 1 1))'));
       
      SELECT ST_DIMENSION(ST_INTERSECTION(t1.geom, t2.geom)), ST_OVERLAPS(t1.geom, t2.geom) FROM t1, t2;
      -- expected:{0, f}
      -- actual  :{0, t}
      

      As described above, the intersection of two polygons is only one point, but MariaDB considers them to be overlapping.

      Attachments

        Issue Links

          Activity

            There are no comments yet on this issue.

            People

              Gosselin Dave Gosselin
              nbvfgh Shijie Li
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.