Skip to main content
Solved

Problem overlapping lines in DWG File

  • February 12, 2019
  • 8 replies
  • 85 views

arxit
Contributor
Forum|alt.badge.img+5
  • Contributor
  • 34 replies

Hello,

 

I have a problem to find overlapping lines with FME, in a DWG file :

 

If there are common vertices between lines, SpatialRelator (or SpatialFilter) works.

Wheareas, if there is no common vertex, overlaps are not found.

 

I tried LineOnLineOverlayer, Intersector and TopologyBuilder, but They have not fixed the problem.

I read these articles, but I didn't find a solution :

https://knowledge.safe.com/questions/1633/intersector-overlap-issue.html

https://knowledge.safe.com/questions/58290/find-overlapping-lines-in-network.html

 

Is there another solution to do this ?

 

Thank you.

Best answer by gio

@arxit

That is because the line do not have same function. ..and do not intersect.

 

Check their angles, they differ after the 10 decimal.:

Angle

6.024405345316602

6.024405345377287

 

As @egomm said if you use a tolerance in the LineOnLineOverlayer (0.000000001 or larger works..)

you get your expected result.

 

(You could also round the coordinates, extend the lines, sync the angles, unify the functions etc.)

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

8 replies

ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3429 replies
  • February 12, 2019

Did you have a tolerance set in the intersector?


arxit
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • 34 replies
  • February 12, 2019

I attach a DWG File, only with 2 lines, where the SpatialRelator don't find overlap between them : drawing2.dwg


arxit
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • 34 replies
  • February 12, 2019

Did you have a tolerance set in the intersector?

No tolerance in the intersector


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3429 replies
  • February 12, 2019

No tolerance in the intersector

You didn't set a tolerance, or you don't have that option? With the current version of the intersector, those overlapping segments are found if a tolerance is set


gio
Contributor
Forum|alt.badge.img+15
  • Contributor
  • 2252 replies
  • Best Answer
  • February 12, 2019

@arxit

That is because the line do not have same function. ..and do not intersect.

 

Check their angles, they differ after the 10 decimal.:

Angle

6.024405345316602

6.024405345377287

 

As @egomm said if you use a tolerance in the LineOnLineOverlayer (0.000000001 or larger works..)

you get your expected result.

 

(You could also round the coordinates, extend the lines, sync the angles, unify the functions etc.)


arxit
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • 34 replies
  • February 12, 2019

@arxit

That is because the line do not have same function. ..and do not intersect.

 

Check their angles, they differ after the 10 decimal.:

Angle

6.024405345316602

6.024405345377287

 

As @egomm said if you use a tolerance in the LineOnLineOverlayer (0.000000001 or larger works..)

you get your expected result.

 

(You could also round the coordinates, extend the lines, sync the angles, unify the functions etc.)

Yes, it works with a tolerance in the Intersector.

however I tried with a CoordinateRounder before the SpatialRelator, but it don't find Overlaps.


arxit
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • 34 replies
  • February 12, 2019

You didn't set a tolerance, or you don't have that option? With the current version of the intersector, those overlapping segments are found if a tolerance is set

I didn't set a tolerance


arxit
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • 34 replies
  • February 12, 2019

I didn't set a tolerance

Thank you, it works with a tolerance