point 基本 ensure span ted zed topo acc rman

Thursday, March 14, 2013

How to Jam an Arrangement_2 into a General_polygon_set_2

I spent about three hours yesterday tracking down a weird bug in CGAL - I have code that builds a general polygon set out of an arrangement, exports the polygons, and weirdly the polygons had duplicate points. This is an impossibility for a valid arrangement.

昨天我花了近3個小時追蹤一個怪異的CGAL的bug——我寫那個程序是為了從arrangement中構建出多邊形的集合，然後導出這些多邊形，而奇怪的多邊形 會有反復點，但在有效的arrangement裏這是不可能的。

To my annoyance, I discovered today as I went to write the bug up that I knew about this bug...over three years ago. :-( I get annoyed when I search for the answer to an obscure OpenGL problem and find my own post (e.g. I‘m not going to find anything I didn‘t already know), but it‘s even more annoying to waste hours on the bug and then have that happen.
讓我氣憤只是的是。我今天去記錄這個問題是發現我事實上在三年前就遇到過了。:-(當我搜索明顯的OpengGL問題然後發現了自己的博文（我不會找到不論什麽我不知道的）。可是更令人火大的是我居然花了數小時調代碼並產生這個錯誤。
Basically if you are going to build a general polygon set by providing a pre-built arrangement, there are two things you must do:

• Remove redundant edges - the GPS code assumes that the arrangement doesn‘t have needless edges (which will screw up traversal). Fortunately, the GPS code has a utility to do this, which I just call.
• Then you have to ensure that the direction of the underlying curves along the various edges are consistent - that is, for a given counter-clockwise boundary, every underlying curve goes either with or against the edge.

(After redundant edge removal, the arrangement will contain no antennas, so it will always be possible to get consistency on both sides of a CCB.)
基本上。假設你要從一個預先構建的arrangement中拿出通用多邊形集合。有兩件事必須做： 移除冗余邊——GPS代碼默認arrangement不須要的邊（它們會搞亂遍歷過程）幸運的是GPS碼有一個輔助函數供我調用幫助完畢這一工作。 然後你必須確保作為各邊基線的曲線的方向是連續的——即給定順時針方向的邊界。每個基礎曲線都順著或逆向於該邊界。

I wrote code to enforce this second condition by flipping the curve of any halfedge where (1) the curve goes against the halfedge and (2) the halfedge is adjacent to the "contained" side of the map.

With this, polygon set operations work on arbitrary map input.

Why Did You Try This?

Forcing pre-made arrangements into polygon sets requires sub-classing the general polygon set template instantiation to get direect access to things like the arrangement, and it‘s not particularly safe. It also requires your arrangement to have the containment flag on the face data mixed in. Why go to the trouble? I did this for two reasons:

• Sometimes the polygonal set data I want to process came from an arrangement, and that arrangement is fairly huge. Having to construct the arrangement out of polygons the normal way requires geometry tests - topology data would be lost and rediscovered. For big maps this is really performance-painful.
• I have some operations that work on arrangements that are precursors to boolean sets. For example, the airport surface area data are fundamentally polygon sets (e.g. in the set is the airport surface area) but some of the constructive processing (e.g. simplifying the contour) run on arrangements.

When an arrangement is turned into a polygon set, one of the results is a rather drastic map cleaning. Since the polygon set cares only about containment (what points are in, what are out), random features like roads tend to get blown away. Posted by Benjamin Supnik at 12:20 PM

怎樣將Arranged_2壓入General_Polygon_set_2中