# CGAL interoperability

**URL:** https://discourse.vtk.org/t/cgal-interoperability/5985
**Category:** Support
**Created:** [June 13, 2021, 9:45am UTC](https://discourse.vtk.org/t/cgal-interoperability/5985 "2021-06-13T09:45:54Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![bistek](https://discourse.vtk.org/user_avatar/discourse.vtk.org/bistek/32/2344_2.png) [@bistek](https://discourse.vtk.org/u/bistek)
#### Post date: [June 14, 2021, 4:18pm UTC](https://discourse.vtk.org/t/cgal-interoperability/5985/6 "2021-06-14T16:18:45Z")

</div>

For instance intersection between two polydata surfaces seems to be still problematic, based on what I find on [#4769](https://discourse.vtk.org/t/obtaining-the-curve-of-intersection-in-vtk/4769https://discourse.vtk.org/t/obtaining-the-curve-of-intersection-in-vtk/4769), [#1476](https://discourse.vtk.org/t/vtk-boolean-operation-poly-data-filter/1476), [#4747](https://discourse.vtk.org/t/intersection-of-3d-mesh-with-polydata-return-only-intersecting-mesh-region/4747), while vtkCutter works but you need an implicit surface as in [#706](https://discourse.vtk.org/t/intersect-polydata-with-an-implicit-function/706).

Thanks!

---

_[View the full topic](https://discourse.vtk.org/t/cgal-interoperability/5985)._