by greenm01

greenm01 / poly2tri

Automatically exported from code.google.com/p/poly2tri

215 Stars 71 Forks Last release: Not found Other 200 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Since there are no Input validation of the data given for triangulation you need

to think about this. Poly2Tri does not support repeat points within epsilon.

* If you have a cyclic function that generates random points make sure you don't

add the same coordinate twice.

* If you are given input and aren't sure same point exist twice you need to

check for this yourself.

* Only simple polygons are supported. You may add holes or interior Steiner points

* Interior holes must not touch other holes, nor touch the polyline boundary

* Use the library in this order:

1) Initialize CDT with a simple polyline (this defines the constrained edges)

2) Add holes if necessary (also simple polylines)

3) Add Steiner points

4) Triangulate

Make sure you understand the preceding notice before posting an issue. If you have

an issue not covered by the above, include your data-set with the problem.

The only easy day was yesterday; have a nice day.




Core poly2tri lib: - Standard Template Library (STL)

Testbed: - gcc - OpenGL - GLFW (http://glfw.sf.net) - Python

waf (http://code.google.com/p/waf/) is used to compile the testbed.
A waf script (86kb) is included in the repositoty.

Building the Testbed

Posix/MSYS environment:

./waf configure ./waf build

Windows command line:

python waf configure python waf build

Running the Examples

Load data points from a file: p2t

Random distribution of points inside a consrained box: p2t random


./p2t dude.dat 300 500 2 ./p2t nazca_monkey.dat 0 0 9

./p2t random 10 100 5.0 ./p2t random 1000 20000 0.025

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.