Apply boolean Polygon clipping operations (intersection, union, difference, xor) to your Polygons & MultiPolygons.
polygon-clipping alternatives and similar libraries
Based on the "Maps" category.
Alternatively, view polygon-clipping alternatives based on common mentions on social networks and blogs.
4.9 0.0 polygon-clipping VS geojson.ioA quick, simple tool for creating, viewing, and sharing spatial data
1.7 3.2 polygon-clipping VS @terraformerA geographic toolkit for dealing with geometry, geography, formats, and building geodatabases
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of polygon-clipping or a related project?
Apply boolean Polygon clipping operations (
xor) to your Polygons & MultiPolygons.
<!-- prettier-ignore-start -->
const polygonClipping = require('polygon-clipping') const poly1 = [[[0,0],[2,0],[0,2],[0,0]]] const poly2 = [[[-1,0],[1,0],[0,1],[-1,0]]] polygonClipping.union (poly1, poly2 /* , poly3, ... */) polygonClipping.intersection(poly1, poly2 /* , poly3, ... */) polygonClipping.xor (poly1, poly2 /* , poly3, ... */) polygonClipping.difference (poly1, poly2 /* , poly3, ... */)
<!-- prettier-ignore-end -->
/* All functions take one or more [multi]polygon(s) as input */ polygonClipping.union (<geom>, ...<geoms>) polygonClipping.intersection(<geom>, ...<geoms>) polygonClipping.xor (<geom>, ...<geoms>) /* The clipGeoms will be subtracted from the subjectGeom */ polygonClipping.difference(<subjectGeom>, ...<clipGeoms>)
Each positional argument (
<geom>) may be either a Polygon or a MultiPolygon. The GeoJSON spec is followed, with the following notes/modifications:
- MultiPolygons may contain touching or overlapping Polygons.
- rings are not required to be self-closing.
- rings may contain repeated points, which are ignored.
- rings may be self-touching and/or self-crossing. Self-crossing rings will be interpreted using the non-zero rule.
- winding order of rings does not matter.
- inner rings may extend outside their outer ring. The portion of inner rings outside their outer ring is dropped.
- inner rings may touch or overlap each other.
For non-empty results, output will always be a MultiPolygon containing one or more non-overlapping, non-edge-sharing Polygons. The GeoJSON spec is followed, with the following notes/modifications:
- outer rings will be wound counter-clockwise, and inner rings clockwise.
- inner rings will not extend outside their outer ring.
- rings will not overlap, nor share an edge with each other.
- rings will be self-closing.
- rings will not contain repeated points.
- rings will not contain superfluous points (intermediate points along a straight line).
- rings will not be self-touching nor self-crossing.
- rings may touch each other, but may not cross each other.
In the event that the result of the operation is the empty set, output will be a MultiPolygon with no Polygons:
The tests are broken up into unit tests and end-to-end tests. The end-to-end tests are organized as GeoJSON files, to make them easy to visualize thanks to GitHub's helpful rendering of GeoJSON files. Browse those tests [here](test/end-to-end).
The Martinez-Rueda-Feito polygon clipping algorithm is used to compute the result in
O((n+k)*log(n)) time, where
n is the total number of edges in all polygons involved and
k is the number of intersections between edges.
Global settings are set via environment variables.
- POLYGON_CLIPPING_MAX_QUEUE_SIZE and POLYGON_CLIPPING_MAX_SWEEPLINE_SEGMENTS: Aims to prevent infinite loops - usually caused by floating-point math round-off errors. Defaults are 1,000,000.
This project adheres to Semantic Versioning.
<!-- prettier-ignore-end -->
The full changelog is available at CHANGELOG.md.
Please contact Mike Fogel if you or your company is interested in sponsoring work on specific bug fixes or feature requests.
- [A new algorithm for computing Boolean operations on polygons](paper.pdf) by Francisco Martinez, Antonio Jesus Rueda, Francisco Ramon Feito (2009)
*Note that all licence references and agreements mentioned in the polygon-clipping README section above are relevant to that project's source code only.