bp_overlay_polygon

Geometric functions bp_overlay_polygon

syntax

  • bp_overlay_polygon (first_polygon_data_item, second_polygon_data_item) (formerly known as Overlay_polygon, a name that was removed in GeoDMS 18.0.0)
  • bp_overlay_polygon (polygon_data_item): the pairs within one polygon set, each pair once (first_rel < second_rel), with their intersection geometry. Since GeoDMS 15.7.0.

description

bp_overlay_polygon(first_polygon_data_item, second_polygon_data_item) results in a new uint32 Domain unit with an entry for each intersecting part of the first_polygon_data_item and the second_polygon_data_item.

The function generates three subitems for the new domain unit:

  • geometry: the Geometry of the resulting polygons (in the figure the yellow polygons). This Attribute has the same Values unit as the first_polygon_data_item and second_polygon_data_item attributes.
  • first_rel: a relation for the new domain unit towards the domain of the first_polygon_data_item.
  • second_rel: a relation for the new domain unit towards the domain of the second_polygon_data_item.

In QGIS, this operation is known as intersect.

Two polygons form a pair when their intersection has an area, that is when they have a common interior point. Polygons that only touch, along a shared edge or at a single point, are not a pair; geos_overlay_polygon differs there. When only the pairing is needed and not the geometry, bp_polygon_connectivity finds the same pairs as relations only.

Suggestion: Set as the right-side argument the set with the largest cardinality. This should give the most efficient result.

It is similar to:

unit<uint32> CartesianProduct := combine(DomainUnit(first_polygon_data_item), DomainUnit(second_polygon_data_item))
{
    attribute<ValuesUnit(first_polygon_data_item)> Geometry(poly) := first_polygon_data_item[first_rel] * second_polygon_data_item[second_rel];
    attribute<bool>   IsIntersecting := area(Geometry, float64) > 0.0;
}
unit<uint32> result := select(CartesianProduct/IsIntersecting)
{
    attribute<DomainUnit(first_polygon_data_item)> first_rel := collect_by_cond(., CartesianProduct/first_rel);
    attribute<DomainUnit(second_polygon_data_item)> second_rel := collect_by_cond(., CartesianProduct/second_rel);
    attribute<ValuesUnit(first_polygon_data_item)> Geometry(poly) := collect_by_cond(., CartesianProduct/Geometry);
}

conditions

  1. The composition type of the first_polygon_data_item and second_polygon_data_item arguments needs to be polygon with an ipoint or spoint Value type.
  2. The Values unit of the first_polygon_data_item and second_polygon_data_item arguments must match.
  3. The order of the points in the first_polygon_data_item and second_polygon_data_item needs to be clockwise for exterior bounds and counterclockwise for holes in polygons (right-hand-rule).

This function results in problems for (integer) coordinates larger than 2^25 (after translation where the first point is moved to (0, 0)). If your integer coordinates, for instance, represent mm, 2^25[mm] = about 33 [km]. The reason is that for calculating intersections, products of coordinates are calculated and cast to float64 with a 53-bit mantissa (in the development/test environment of boost::polygon, these were float80 values with a 64-bit mantissa). We advise you to keep the size of your integer coordinates for polygons limited and, for instance, do not use an mm precision for country borders (a meter or kilometre might be sufficient).

since version

15.6.0

example 

unit<uint32> intersect := bp_overlay_polygon(Building/geometry, District/geometry);

see also