MakeValid() polygon to multi-polygon raises error in GEOS C function "GEOSGetNumInteriorRings_r".

[Eran Keydar]

I have model with Polygon field.
Using MakeValid on the polygon field returns MultiPolygon, but the resulting geom is broken.

This worked on 1.11 and failed on 2.2

A simple solution is to make the fix on MultiPolygon field (with single polygon).

This is the model (app1/models.py):

from django.contrib.gis.db import models
class WithPolygon(models.Model):
    geom = models.PolygonField()

Then I run the following code:

def fix_polygon():
    import django
    from django.contrib.gis.db.models.functions import MakeValid
    from django.contrib.gis.geos import MultiPolygon, Polygon
    from app1.models import WithPolygon
    print('version = {}'.format(django.__version__))
   # create disjoint rings
    r1 = [[0,0],[100,0],[100,100],[0, 100], [0,0]]
    r2 = [[x+1000,y+1000] for x,y in r1]
   #  create polygon with two rings
    p1 = Polygon(r1, r2)
    print('p1.valid  = {}'.format(p1.valid))  # False
    print('p1.valid_reason =  {}'.format(p1.valid_reason)) # Hole lies outside shell[1000 1000]
    wp1 = WithPolygon.objects.create(geom=p1)
    wp1_with_fix = WithPolygon.objects.annotate(v=MakeValid('geom')).filter(id=wp1.id)[0]
    mp = wp1_with_fix.v
    print('mp.geom_type = {}'.format(mp.geom_type)) # MultiPolygon
    print('mp.__class__ = {}'.format(mp.__class__)) # returns Polygon in 2.2 MultiPolygon in 1.11
    print(len(mp))  # GESOEXception in 2.2, (In 1.11 prints 2)

Outputs are attached.

[Carlton Gibson]

Hi Eran,

Can I ask you to double check that the only difference is your Django version here? Most of the functions, including MakeValid are just wrappers around the DB functionality or the underlying C GEOS library.

I can´t see a relevant change from the provided stack trace between 1.11 and 2.2 (git difftool 1.11 2.2 -- django/contrib/gis).

We have ​a test case for MakeValid here. It's similar, but not exactly equivalent to your case.

[Eran Keydar]

The only difference is the Django version.

The difference is that in test suite, a polygon is fixed to polygon, while in my case a polygon is fixed into multi polygon.

I've added the following test case and then ran it with the django git, with branch stable/1.11.x stable/2.2.x and mater
It failed on both master and 2.2.x but passed on 1.11.x

    @skipUnlessDBFeature("has_MakeValid_function")
    def test_make_valid2(self):
        invalid_geom = Polygon(
            ((0,0),(0,1),(1,1),(1,0),(0,0)),
            ((10,0),(10,1),(11,1),(11,0),(10,0)),
        )
        State.objects.create(name='invalid', poly=invalid_geom)
        invalid = State.objects.filter(name='invalid').annotate(repaired=functions.MakeValid('poly')).first()
        self.assertIs(invalid.repaired.valid, True)
        self.assertEqual(invalid.repaired.geom_type,'MultiPolygon')
        self.assertEqual(len(invalid.repaired), 2)

[Mariusz Felisiak]

Thanks for tests.

Regression in 2ef4b4795e29be8c33a6de9cc0c05b59025d13a5.

[Sergey Fedoseev]

​PR

[Mariusz Felisiak <felisiak.mariusz@…>]

In a920c0b8:

Fixed #31142 -- Fixed MakeValid.output_field when geometry type is changed.

Regression in 2ef4b4795e29be8c33a6de9cc0c05b59025d13a5.