Opened 6 years ago

Last modified 3 months ago

#3042 new enhancement

Add edge-linking checks in ValidateTopology

Reported by: strk Owned by: strk
Priority: medium Milestone: PostGIS Fund Me
Component: topology Version: master
Keywords: Cc: remic

Description

The ValidateTopology? function does not currently check if edge linking is correct. It probably should.

See http://trac.osgeo.org/postgis/ticket/1224#comment:5

Change History (6)

comment:1 Changed 5 years ago by strk

Milestone: PostGIS 2.2.0PostGIS Future

comment:2 Changed 3 years ago by robe

Milestone: PostGIS FuturePostGIS Fund Me

Milestone renamed

comment:3 Changed 3 months ago by strk

For reference, #4709 is a bad consequence (backend crash) of a topology with edge-linking corruption, so dealing with it with ValidateTopology? becomes more important.

comment:4 Changed 3 months ago by Sandro Santilli <strk@…>

In 2ce98e2/git:

Handle non-closed edge rings by human readable error

Handle both topological and geometrical corruption

Have getRingEdges raise an error if topology is corrupted

References #4709
References #3042

comment:5 Changed 3 months ago by laopsahl

Another problem with function is that uses a lot of time .

Does make a sense to make optimal parameter bbox to limit the area to check ?

comment:6 Changed 3 months ago by strk

There are a number of validity checks that could be performed within a limited bounding box yes, I'm thinking of:

  • Edge linking (for all nodes falling in the bbox)
  • Consistent side-labelling for linked edges
Note: See TracTickets for help on using tickets.