Skip to main content
Question

convert DGN igds_3d_solid to 2d

  • July 30, 2019
  • 2 replies
  • 40 views
T
Forum|alt.badge.img

My client has several dgn files that contain 3d_solid objects (pipelines and other vector data). I have a workbench on our FME Server that will convert drawings into shapefiles but the solid objects are not going through. The igds_type is igds_3d_solid until I try aggregate them or assign them to 3D or 2D.

One thing I also notice is that on some of the geometries not reading through the igds_type does not equal the fme_geometry. For example, I look at the dgn before processing and one of the vectors is igds_type = igds_line, but the fme_geometry = fme_polygon.

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.

2 replies

andreaatsafe
Safer
Forum|alt.badge.img+14
  • andreaatsafeSafer
  • Safer
  • 450 replies
  • August 2, 2019

Hi @tsurveyor,

When you are writing the data to shapefile, are you handling both 2D and 3D geometry types at the same time? If you are wanting to convert the solids to 2D, I think you'll want to use a 2DForcer and/or GeometryCoercer to coerce the solids to 2D (lines?).

The Shapefile writer has a parameter "Output Dimension" that defines the dimension of the features which is by default set to "Dimension From First Feature" so if you are handling 2D data at the same time, I suspect the 3D solids are getting rejected because of this parameter. Perhaps if you have multiple geometries this is parameter is affecting writing out the 3D data. Regardless, if you are wanting to have the solids represented in 2D, you'll need to force/coerce the 3D data into 2D prior to write.

Would be good to see the workspace too, if you are able to share it here. If not, please submit a report via report a problem.

As for the igds_type and fme_geometry not matching, what version of FME are you using? If you are using the latest FME 2019.1, and this is occurring, we'll want to look into this further. If you can share a sample DGN file of this happening that would be great (either on the forum or via the report a problem page).

- Andrea

T
Forum|alt.badge.img
  • tsurveyor
  • Author
  • 49 replies
  • August 2, 2019

Hi @tsurveyor,

When you are writing the data to shapefile, are you handling both 2D and 3D geometry types at the same time? If you are wanting to convert the solids to 2D, I think you'll want to use a 2DForcer and/or GeometryCoercer to coerce the solids to 2D (lines?).

The Shapefile writer has a parameter "Output Dimension" that defines the dimension of the features which is by default set to "Dimension From First Feature" so if you are handling 2D data at the same time, I suspect the 3D solids are getting rejected because of this parameter. Perhaps if you have multiple geometries this is parameter is affecting writing out the 3D data. Regardless, if you are wanting to have the solids represented in 2D, you'll need to force/coerce the 3D data into 2D prior to write.

Would be good to see the workspace too, if you are able to share it here. If not, please submit a report via report a problem.

As for the igds_type and fme_geometry not matching, what version of FME are you using? If you are using the latest FME 2019.1, and this is occurring, we'll want to look into this further. If you can share a sample DGN file of this happening that would be great (either on the forum or via the report a problem page).

- Andrea

Thanks Andrea. I can't post the workbench here but will send the files. The transformers I tried are 3DForcer, 2DForcer, GeometryValidator, SurfaceNormalExtractor, GeommetryCoercer.

Community Stats

32,080
Posts
121,818
Replies
39,714
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.