Skip to main content
Question

Snipper point in exit

  • April 10, 2018
  • 8 replies
  • 43 views
geo-x
Supporter
Forum|alt.badge.img+6

Hello everybody.

I've a question with the transformer Snipper.

Before transformer I've lines with start and end measure.

My transformer parameters are :

After transformer I've cut lines with the start and end measure of before and points alones.

I don't understand why I've points in exit have you got any idea ?

Thank you for your help.

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

david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • April 10, 2018

Can you give us a concrete example of a line, including m-values, and some values for "_measure" and "_end_measure"?

Or even better, post a sample workspace with a small test dataset that demonstrates the issue.

gio
Contributor
Forum|alt.badge.img+15
  • gioContributor
  • Contributor
  • 2252 replies
  • April 10, 2018

Might you have fed it the lines which are defined by their start and end measures already?

Then it might snip them at the begin and end, yielding points if it is not exactly the same as the true location of the vertices of the lines, you might end up with point or point like features.

That's why you can use begin and start instead.

Or your maybe start and end measures are equal.

Geuss sample data is idd a good idea.

geo-x
Supporter
Forum|alt.badge.img+6
  • geo-xSupporter
  • Author
  • Supporter
  • 89 replies
  • April 11, 2018

Thanks for the test data and workspace, that's very helpful. There are at least two different problems with the values given to the Snipper, as seen in the shapefile:

  • Sometimes the start/end measures are out of range compared to line. This is shown in the FME log, e.g. "@Snip (or FMELine::snip) was given Measures of 0.0390917661 and 0.0390917661, which are out of range for a line with min/max measures of 0 and 0.006715436606972919. Snapping params to closest valid value." If both the start and end measure is outside the scope of the line (as is the case here), you'll end up with a zero-length line = a point.

     

  • There are lots of features where the start and end measure is identical, meaning that you'll end up with a zero-length line = a point.

You may want to take a closer look at the algorithm that calculates the start and end measures for the Snipper.

Thank you for your help, this is an extract for testing : forums-tests.zip

geo-x
Supporter
Forum|alt.badge.img+6
  • geo-xSupporter
  • Author
  • Supporter
  • 89 replies
  • April 11, 2018

Thank you for your help, this is an extract for testing : forums-tests.zip

In fact I think because I've the same start and end coordinate, but why I've lines and points and not lines or nothing ?

 

 

david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • April 11, 2018

Thanks for the test data and workspace, that's very helpful. There are at least two different problems with the values given to the Snipper, as seen in the shapefile:

  • Sometimes the start/end measures are out of range compared to line. This is shown in the FME log, e.g. "@Snip (or FMELine::snip) was given Measures of 0.0390917661 and 0.0390917661, which are out of range for a line with min/max measures of 0 and 0.006715436606972919. Snapping params to closest valid value." If both the start and end measure is outside the scope of the line (as is the case here), you'll end up with a zero-length line = a point.

     

  • There are lots of features where the start and end measure is identical, meaning that you'll end up with a zero-length line = a point.

You may want to take a closer look at the algorithm that calculates the start and end measures for the Snipper.

geo-x
Supporter
Forum|alt.badge.img+6
  • geo-xSupporter
  • Author
  • Supporter
  • 89 replies
  • April 11, 2018

Thanks for the test data and workspace, that's very helpful. There are at least two different problems with the values given to the Snipper, as seen in the shapefile:

  • Sometimes the start/end measures are out of range compared to line. This is shown in the FME log, e.g. "@Snip (or FMELine::snip) was given Measures of 0.0390917661 and 0.0390917661, which are out of range for a line with min/max measures of 0 and 0.006715436606972919. Snapping params to closest valid value." If both the start and end measure is outside the scope of the line (as is the case here), you'll end up with a zero-length line = a point.

     

  • There are lots of features where the start and end measure is identical, meaning that you'll end up with a zero-length line = a point.

You may want to take a closer look at the algorithm that calculates the start and end measures for the Snipper.

Maybe this is when I build the shapefile because in my treatment I don't have this message

 

 

geo-x
Supporter
Forum|alt.badge.img+6
  • geo-xSupporter
  • Author
  • Supporter
  • 89 replies
  • April 12, 2018

Thanks for the test data and workspace, that's very helpful. There are at least two different problems with the values given to the Snipper, as seen in the shapefile:

  • Sometimes the start/end measures are out of range compared to line. This is shown in the FME log, e.g. "@Snip (or FMELine::snip) was given Measures of 0.0390917661 and 0.0390917661, which are out of range for a line with min/max measures of 0 and 0.006715436606972919. Snapping params to closest valid value." If both the start and end measure is outside the scope of the line (as is the case here), you'll end up with a zero-length line = a point.

     

  • There are lots of features where the start and end measure is identical, meaning that you'll end up with a zero-length line = a point.

You may want to take a closer look at the algorithm that calculates the start and end measures for the Snipper.

In fact yes I've this problem, and I don't know why because I extract a measure from line to point with PointOnLineOverlayer and after I use Featuremerger and Snipper like the treatment dynamic-line-segmentation-2.fmwt describe here

 

 

geo-x
Supporter
Forum|alt.badge.img+6
  • geo-xSupporter
  • Author
  • Supporter
  • 89 replies
  • April 12, 2018
In fact yes I've this problem, and I don't know why because I extract a measure from line to point with PointOnLineOverlayer and after I use Featuremerger and Snipper like the treatment dynamic-line-segmentation-2.fmwt describe here

 

 

I found the problem I've duplicate geometry !

 

 

Community Stats

32,087
Posts
121,852
Replies
39,729
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.