3rd-party/poly2tri
1
0
Fork 0
mirror of https://github.com/jhasse/poly2tri.git synced 2024-11-05 22:09:52 +01:00
Code Issues Projects Releases Wiki Activity
2D constrained Delaunay triangulation library
286 Commits 1 Branch 0 Tags 2.4 MiB
C++ 94.2%
C 3.7%
CMake 1.5%
Meson 0.6%
19ec7c78a1
Go to file
Roy Stogner 19ec7c78a1 ConcaveBoundaryTest unit test 
This is from the case I originally got to trigger the problem.  We could
probably boil it down to something smaller (by temporarily reverting the
Orient2d change to make sure the failure still occurs) but this doesn't
seem too bloated for a unit test as-is.
2022-03-15 20:37:14 -05:00
.github/workflows Add CMake files for the unit tests 2020-08-27 19:16:17 +02:00
.vscode Add debug configurations for VSCode 2020-10-19 18:27:52 +02:00
doc Add references section to README 2020-10-26 20:58:49 +01:00
poly2tri Disable tolerance in Orient2d collinearity test 2022-03-15 19:16:40 -05:00
testbed Rename testbed/testbed to testbed/p2t 2021-12-01 17:36:31 -06:00
unittest ConcaveBoundaryTest unit test 2022-03-15 20:37:14 -05:00
.clang-format Add .clang-format 2020-10-19 18:24:46 +02:00
.gitignore Ignore .cache/ 2020-12-17 23:13:20 +01:00
AUTHORS modified Authors file 2010-01-30 13:10:18 -05:00
CMakeLists.txt Add headers in project files generated by cmake 2020-10-26 12:07:44 +01:00
LICENSE Change BSD-3 license formatting a little bit so that GitHub detects it 2018-09-11 13:00:49 +02:00
meson.build Add CMake files for the unit tests 2020-08-27 19:16:17 +02:00
README.md Consistent executable path in README.md 2021-12-01 17:38:53 -06:00

README.md

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.

TESTBED INSTALLATION GUIDE

Dependencies

Core poly2tri lib:

  • Standard Template Library (STL)

Unit tests:

  • Boost (filesystem, test framework)

Testbed:

Build the library

With the ninja build system installed:

mkdir build && cd build
cmake -GNinja ..
cmake --build .

Build and run with unit tests

With the ninja build system:

mkdir build && cd build
cmake -GNinja -DP2T_BUILD_TESTS=ON ..
cmake --build .
ctest --output-on-failure

Build with the testbed

mkdir build && cd build
cmake -GNinja -DP2T_BUILD_TESTBED=ON ..
cmake --build .

Running the Examples

Load data points from a file:

build/testbed/p2t <filename> <center_x> <center_y> <zoom>

Random distribution of points inside a constrained box:

build/testbed/p2t random <num_points> <box_radius> <zoom>

Examples:

build/testbed/p2t testbed/data/dude.dat 300 500 2
build/testbed/p2t testbed/data/nazca_monkey.dat 0 0 9

build/testbed/p2t random 10 100 5.0
build/testbed/p2t random 1000 20000 0.025

References

  • Domiter V. and Zalik B. (2008) Sweep‐line algorithm for constrained Delaunay triangulation
  • FlipScan by library author Thomas Åhlén

FlipScan