Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

rkmcswain
657 Vistas, 4 Respuestas

DGNIMPORT creates duplicate blocks with diff names

AutoCAD/Civil 3D 2014

 

When we import a DGN file that contains multiple insertions of the same cell, each insertion becomes a differently named BLOCK after the import.

 

In some cases, there are hundreds of insertions of a particular cell/block which means in the DWG, instead of having hundreds of insertions of a single block definition, we end up with hundreds of block definitions, each inserted once.

 

Here is a Microstation dialog showing 2 of the same named cells (there are about 20 of these cells inserted in the DGN)

 

 

Here is the result (list of blocks) after DGNIMPORT. Each one of the "Check?" blocks are the same.

 

 

 

 

If we open the DGN in Microstation and then save as a DWG, the result is better, meaning that not all of the cells are treated this way, but it still does the same thing to *some* of them. There doesn't seem to be any rhyme or reason for this.

 

The end user wants to edit this block one time and have all the insertions update, but that's impossible of course when this happens.

 

Any thoughts?

 

 

 

 

R.K. McSwain     | CADpanacea | on twitter
Etiquetas (4)
ToddRogers-WPM
en respuesta a: rkmcswain

In Civil 3D, use MAPIMPORT instead of DGNIMPORT.  It's much cleaner and the projection won't be thrown off.  Make sure to check the box to Import Polygons as Closed Polylines.

Todd Rogers
artc2
en respuesta a: rkmcswain

Are the cells, perhaps, not shared cells, so they are translated as separate blocks?
rkmcswain
en respuesta a: ToddRogers-WPM

TRogers wrote:

In Civil 3D, use MAPIMPORT instead of DGNIMPORT.

Same results. Multiple "alike" blocks with different names. Thanks.
R.K. McSwain     | CADpanacea | on twitter
rkmcswain
en respuesta a: artc2

artc2 wrote:
Are the cells, perhaps, not shared cells, so they are translated as separate blocks?

I believe you're on to something here.

 

I found this, but not sure if there is anything we can do to the original DGN file to fix this.

 

Thanks.

 

 

 

 

 

 

 

 

 

R.K. McSwain     | CADpanacea | on twitter