Skip to main content
“line string or poly boundary is self-intersecting” error,

 

 

On our workflow, the CAD hatches that represent the Landuse are converted to polygons and then these polygons are collected in one layer stored in ESRI enterprise geodatabase.

 

 

As the FME is applied to convert the hatches of CAD to GIS polygons, these generated polygons by the FME introduce error as they are copied and pasted to the destination layer in the enterprise geodatabase.

 

 

 

CAD file:

 

http://www.mediafire.com/download/x7plx8ka56kg9ai/AsSamou_Hebron_MasterPlan_05_X_02.dwg

 

 

 

 

 

The workbench is:

 

 

 

Error in ArcGIS (as the layer is copied and pasted)

 

 

 

 

Which command should be included in the workbench to avoid such error?

 

 

Thank you

 

 

Best

 

 

Jamal
Hi,

 

 

the GeometryValidator has an option to fix 2D self-intersects. Be sure to do it just before the output, so you don't snap or clip the geometries after the repair.

 

 

David
Unfortunately, checking the “self-intersections” in 2D doesn’t solve the issue

 

 

 

The Landuse polygons

 

 

 

 

The Boundary polygon

 

 

 

The Roads polygon (Roads = Boundary – Landuse)

 

 

 

 

The combination of Roads and Landuse (Roads + Landuse)

 

 

 

 

The error as the Roads and Landuse are copied and pasted to the DESTINATION enterprise Geodatabase layer

 

 

 

 


Cont.

 

 

 

What other solutions might still be there?

 

 

FME Workbench:

 

http://www.mediafire.com/view/vnv1ex43575uha1/UrbanMasterPlan_CAD_To_GIS_15.fmw

 

 

 

 

 

Excel file for mapping:

 

http://www.mediafire.com/view/m9j7828verq26nk/UrbanMasterPlanDomain_FME_18.xls

 

 


Hi Jamal, have you tried "Check Self-Touching Polygon" parameter?

 

 

 

Takashi
Thanks Takashi,

 

 

I tried it and I got the error below

 

 

 

 

 

 

 

 

I thank that the error now is with the Roads layer that it derived from the Boundary and Landuse layers

 

 

Roads = Boundary – Landuses

 

 

I tried to copy and paste the Roads layer (only) and I got the same error.

 

 

How to fix these very frustrating errors?
I guess the reason is existence of very narrow parts of the donut polygon. The GeometryValidator seems not to be able to repair it perfectly.

 

In such a case, my last resort is to use the Bufferer to shrink the boundary a slight.

 

 


Thank you very much Takashi.

 

 

It appears that “bufferer” has resolved my issue. It works like a charm

 

 

Best

 

 

Jamal

 

 


Reply