Class OverlapUnion
- java.lang.Object
-
- org.locationtech.jts.operation.union.OverlapUnion
-
public class OverlapUnion extends java.lang.Object
Deprecated.due to impairing performanceUnions MultiPolygons efficiently by using full topological union only for polygons which may overlap, and combining with the remaining polygons. Polygons which may overlap are those which intersect the common extent of the inputs. Polygons wholly outside this extent must be disjoint to the computed union. They can thus be simply combined with the union result, which is much more performant. (There is one caveat to this, which is discussed below).This situation is likely to occur during cascaded polygon union, since the partitioning of polygons is done heuristically and thus may group disjoint polygons which can lie far apart. It may also occur in real world data which contains many disjoint polygons (e.g. polygons representing parcels on different street blocks).
Algorithm
The overlap region is determined as the common envelope of intersection. The input polygons are partitioned into two sets:- Overlapping: Polygons which intersect the overlap region, and thus potentially overlap each other
- Disjoint: Polygons which are disjoint from (lie wholly outside) the overlap region
Discussion
In general the Overlapping set of polygons will extend beyond the overlap envelope. This means that the union result will extend beyond the overlap region. There is a small chance that the topological union of the overlap region will shift the result linework enough that the result geometry intersects one of the Disjoint geometries. This situation is detected and if it occurs is remedied by falling back to performing a full union of the original inputs. Detection is done by a fairly efficient comparison of edge segments which extend beyond the overlap region. If any segments have changed then there is a risk of introduced intersections, and full union is performed.This situation has not been observed in JTS using floating precision, but it could happen due to snapping. It has been observed in other APIs (e.g. GEOS) due to more aggressive snapping. It is more likely to happen if a Snap-Rounding overlay is used.
NOTE: Test has shown that using this heuristic impairs performance. It has been removed from use.
- Author:
- mbdavis
-
-
Constructor Summary
Constructors Constructor Description OverlapUnion(Geometry g0, Geometry g1)
Deprecated.Creates a new instance for unioning the given geometries.OverlapUnion(Geometry g0, Geometry g1, UnionStrategy unionFun)
Deprecated.
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description Geometry
union()
Deprecated.Unions the input geometries, using the more performant overlap union algorithm if possible.static Geometry
union(Geometry g0, Geometry g1, UnionStrategy unionFun)
Deprecated.Union a pair of geometries, using the more performant overlap union algorithm if possible.
-
-
-
Constructor Detail
-
OverlapUnion
public OverlapUnion(Geometry g0, Geometry g1)
Deprecated.Creates a new instance for unioning the given geometries.- Parameters:
g0
- a geometry to uniong1
- a geometry to union
-
OverlapUnion
public OverlapUnion(Geometry g0, Geometry g1, UnionStrategy unionFun)
Deprecated.
-
-
Method Detail
-
union
public static Geometry union(Geometry g0, Geometry g1, UnionStrategy unionFun)
Deprecated.Union a pair of geometries, using the more performant overlap union algorithm if possible.- Parameters:
g0
- a geometry to uniong1
- a geometry to unionunionFun
-- Returns:
- the union of the inputs
-
union
public Geometry union()
Deprecated.Unions the input geometries, using the more performant overlap union algorithm if possible.- Returns:
- the union of the inputs
-
-