Skip to main content
Solved

Order of Vertices forming lines and polygons

  • September 16, 2019
  • 2 replies
  • 130 views

deanhowell
Influencer
Forum|alt.badge.img+23

Hello All,

I have found a few great posts that helped me get the order of vertices in a polygon but am trying to work out the how to get the start and end coordinates in correct order.

My workflow is as follows:

1. Read in polygon features

2. Use Chopper and counter to break into points and attribute.

3. Use Chopper and counter to break into lines

4. Use PointOnLineOverlayer to get the start and end coordinated.

5. Attribute lines with Start and End point ids.

 

What I am finding is that the start end end points are correct but the order in the line table is not.

In the example below, I have a triangular parcel where it goes from point 81736 to 81735 to 81750, so I hoping to get something like

1 - 81750 to 81735

2 - 81735 to 81736

3 - 81736 to 81750

but am getting the following

 

Any assistance would be greatly appreciated.

 

Here is the workspace that I am working on

Best answer by takashi

Hi @deanhowell, if I understood your requirement correctly, this workflow example might help you.

add-from-to-pointno-to-line-segments.fmw (FME 2019.1.2)

View original
Did this help you find an answer to your question?

2 replies

takashi
Influencer
  • Best Answer
  • September 16, 2019

Hi @deanhowell, if I understood your requirement correctly, this workflow example might help you.

add-from-to-pointno-to-line-segments.fmw (FME 2019.1.2)


deanhowell
Influencer
Forum|alt.badge.img+23
  • Author
  • Influencer
  • September 16, 2019
takashi wrote:

Hi @deanhowell, if I understood your requirement correctly, this workflow example might help you.

add-from-to-pointno-to-line-segments.fmw (FME 2019.1.2)

Thanks @takashi, that does the trick perfectly. Thanks for helping me solve another piece of the puzzle.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings