Skip to Content.
Sympa Menu

cgal-discuss - Re: [cgal-discuss] How to improve the speed of polygons offsetting in CGAL?

Subject: CGAL users discussion list

List archive

Re: [cgal-discuss] How to improve the speed of polygons offsetting in CGAL?


Chronological Thread 
  • From: Fernando Cacciola <>
  • To:
  • Subject: Re: [cgal-discuss] How to improve the speed of polygons offsetting in CGAL?
  • Date: Mon, 30 Aug 2010 13:17:00 -0300
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=SrsXth3rcY/m3y/25lpcv28vClBg2WH2O0M4PZ6R0eDj6zbtSIVB2LcMPfXNBk9bh/ hZaaBsZ1Mu+/MFtFxS5/Sr9ej7XcTs7REyP0dmOKEVqH4bLSqWwlnEIVKRWX+F0it9/q 1wGN7Di7MstGlWr1gEBMRJzQzRFZGA8qP30So=
Hi Ben,

> Hi Y'all,
>
> Fernando would be the expert on computation time, but...if the goal is an
> offset, an alternative to a straight skeleton would be to do a 'buffer' type
> operation, e.g. construct the offset curves piece-wise, dump them in an
> arrangement, and use the arrangement to find the interior.
>

FWIW, in CGAL 3.6, when you use the API that constructs offset curves
directly (that is, when the straight skeleton is constructed under the
hood), the skeleton is created only *partially*, just far enough to
contain the offsets at the given distance.
AFAICT this procedure should result in an effective running time even
faster then using an arrangement.

OTOH, if the *entire* skeleton is constructed, this can take up much
much more time.

Best

--
Fernando Cacciola
SciSoft Consulting, Founder
http://www.scisoft-consulting.com

Archive powered by MHonArc 2.6.16.

Top of Page