I am using an AutoDesk Revit Reader to transfer an RVZ file to a Feature Class in an ESRI GEoDatabase (ArcObjects). When using the 2DForcer to transform the 3D RVZ data to 2D data the translation fails and there error I get is 'Cannot write a non-area feature to an area feature class.' I am using a Geometry Filter which has the solid and area options checked, followed by a GeometryValidator with all options checked. and the output feature class type is set to polygon.
Solved
Cannot write a non-area feature to an area feature class
Best answer by erik_jan
The issue with going from 3D to 2D is usually that vertical lines become points and vertical areas become lines.
Sounds like that is the case for some of your features.
And the ESRI geodatabase is very picky about those geometry types.
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.
+6- Safer
- 278 replies
Hello @rralbritton, would you mind attaching your workspace and maybe a small sample of data(1 feature in FFS format would work).
Alternatively, the output exiting the 2DForcer, what is the geometry listed as?
+22- Contributor
- 2179 replies
- Best Answer
The issue with going from 3D to 2D is usually that vertical lines become points and vertical areas become lines.
Sounds like that is the case for some of your features.
And the ESRI geodatabase is very picky about those geometry types.
The issue with going from 3D to 2D is usually that vertical lines become points and vertical areas become lines.
Sounds like that is the case for some of your features.
And the ESRI geodatabase is very picky about those geometry types.