This is a classic example revealing the (slight) inconsistency of the spatial predicates compared to the spatial overlay operations (in PostGIS, and the underlying GEOS and JTS geometry libraries). The reason for this is due to numerical precision issues with finite floating-point representation of real numbers. Because the spatial predicates return ...
Resolving spatial relationships between adjacent geometries which do not share exactly same vertices tends to be a bit unreliable because of inaccuracy of floating point computing. In this case the first polygon (on the right) does not have a vertex around the top-right corner of the second polygon.
The ST_Overlaps and ST_Intersection must create an ...
You can use select by expression to select features on the same layer using the expression get_feature. The expression in this case is (see screenshot where the labels show the valule of the Seeding_Ra attribute for each polygon):
If you have a point layer and a line layer, then you can count the lines near by the points using field calculator:
Open the attribute table of point layer
Open the field calculator dialog (abacus icon)
Enter the following expression
aggregate( layer:='line', aggregate:='count', expression:="ATTR",filter:= intersects( buffer(geometry(@parent)...
So, your raw data in text format is shown below:
I can't say how to correct the topology automatically but these images should show what happens.
These are the vertices of the left side polygon (clipped1) and the location of the overlap.
These are the vertices of the right side polygon (clipped2) and the location of the overlap.
The overlap is in the middle of the segment of the right side polygon. The ...
The methods mentioned by @Michael Stimson work very well. I tried both ArcGIS and QGIS. The "feature to polygon" in ArcGIS and "Polygon self-intersection" in QGIS do the same thing. They "return a new layer with sub-divided polygons (while only one of the duplicated overlapping area is retained)". The only difference is that in ...