Subject: CGAL users discussion list
List archive
Re: [cgal-discuss] Inset polygon/buffering: straights skeleton vs. arranagement
Chronological Thread
- From: "Fernando Cacciola" <>
- To: <>
- Cc: <>
- Subject: Re: [cgal-discuss] Inset polygon/buffering: straights skeleton vs. arranagement
- Date: Tue, 29 Apr 2008 10:28:22 -0300
- Organization: Geometry Factory
Hi Ben,
Sorry I couldn't respond earlier.
In my old code, where I was only interested in a slightly inset contourThere is now :)
and not the entire skeleton, I got a big performance win by halting the
inset operation once I'd exceeded the "time" that my offset needed.
Basically I could throw out and not evaluate the entire event list.
Is there a way to do this in the CGAL skeleton/offset classes?
I'm just finishing testing a new version of the algorithm which does precisely that: it generates a partial skeleton containing only the events needed to offset at a single known distance.
I tried with some large GIS data and the performance win is significant.
Best
Fernando Cacciola
GeometryFactory
- Inset polygon/buffering: straights skeleton vs. arranagement, Ben Supnik, 04/06/2008
- Re: [cgal-discuss] Inset polygon/buffering: straights skeleton vs. arranagement, Fernando Cacciola, 04/29/2008
Archive powered by MHonArc 2.6.16.