I'm trying to count the vertices on line segments. The data is a .GDB and has complex line segments that contain fillets and arcs. The VertexCounter is calculating an incorrect number of vertices for line segments that contain arcs. Is there a work-around for these more complex line segments?
Question
VertexCounter transformer giving incorrect vertex count on line segments containing arcs.
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.
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.
+46- Influencer
I think a PythonCaller with this check should work:
geom = feature.getGeometry()
if isinstance(geom, fmeobjects.FMEPath):
    # feature geometry is an FMEPath instance
I was thinking of a non-python solution. It seems strange that you can't filter out paths when there are quite a few cases where you might want to treat them differently. I can fudge it with a combination of a GeometryPropertySetter and GeometryPropertyExtractor but i'm surprised there's not a better way
I was thinking of a non-python solution. It seems strange that you can't filter out paths when there are quite a few cases where you might want to treat them differently. I can fudge it with a combination of a GeometryPropertySetter and GeometryPropertyExtractor but i'm surprised there's not a better way
Unfortunately I'm not aware of any non-Python solution either. I agree that it would be handy if e.g. the GeometryFilter allowed you to check for path.
+59- Safer
I was thinking of a non-python solution. It seems strange that you can't filter out paths when there are quite a few cases where you might want to treat them differently. I can fudge it with a combination of a GeometryPropertySetter and GeometryPropertyExtractor but i'm surprised there's not a better way
That's another one I'll raise with the developers. Seems crazy there is no way to tell if a feature is a path. Not even fme_type or fme_geometry will do it.
+59- Safer
I was thinking of a non-python solution. It seems strange that you can't filter out paths when there are quite a few cases where you might want to treat them differently. I can fudge it with a combination of a GeometryPropertySetter and GeometryPropertyExtractor but i'm surprised there's not a better way
Filed as an enhancement request. The only other way I can see is to use GeometryExtractor to output XML and then check for the <path> tag.
+46- Influencer
Filed as an enhancement request. The only other way I can see is to use GeometryExtractor to output XML and then check for the <path> tag.
My fudge was to set a geometry name then use the GeometryPropertyExtractor to only extract path - only paths come out the extracted port then