But i have Always the same message :
Polygon feature must have at least 4 coordinates to be valid for the shape file. The feature will be skipped
REJECTING BELOW FEATURE:
And i dont understand what is really the problem
Can you help me please
thanks
Question
i convert some closed line (from dgn exploded cell) in area and those aeras would be normaly written into a shape
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.
+15- Contributor
@thq
Hi.
It is actually like it said.
A area with just 3 vertices was offered to the shapefile writer.
AS a correct polygon has first = last vertex.
You can check "the below" feature's vertices.
Either filter it out by: vertexcount =<4 and geotype = fme_area.
Or look at it in the feature information window.
Also, mostly after the run, the offending feature is saved in a ffs. It's code can be seen in the Translationlog. You can find it in your fme temp folder.
Maybe some othe features were not as closed as assumed
(in autocad the close function is safer then trying to snap the last vertex.
Fme ruthlessly exposes such errant assumpiotns....;)
When i test areas with vertexcount all areas have 5 vertex
+15- Contributor
When i test areas with vertexcount all areas have 5 vertex
@thq
I assume you counted prior to wrtitin th shapefile, yes?
The problem is generated by areabuilding.
Do you area build using the dgn-id as a group by value?
Or are you generating areas from common boundaries? (no group by possible, unless you got left_right attributes: old-school)
Do you have a sample set with the relevant portion available?
We could have a look-see where the problem resides.