Grouped hole feature created

Hi,

When I attach or open a dgn file containing a mix of complex shapes and grouped holes, Map Manager will create a separate inferred feature for the grouped holes called GHOLE. This feature contains elements from all layers that contains grouped holes. 

Why?

This means that the other layers in Map Manager are incomplete.

/Krister

Parents
  • Hi,

    The attached file contains information on four layers only (the one named TO_), each layer contains a mix of complex shapes and grouped holes. Map Manager creates a singel feature for all grouped holes. If I toggle the display of GHOLE elements on all levels will be affected. Toggle one of the other layers will not affect the grouped holes.

    I'm using Bentley Map 08.11.09.107.

    /Krister

    Owner consultant at Surell Consulting AB

  • Hi,

    Yes. I reproduce the issue you’re reported here.

    As I said, in Map Manager, it will place Grouped Hole on default layer (you: GHOLE me:Level_0) when the Grouped Hole component elements are on different levels. If grouped hole components are all on the same level, map manager will recognize the level as a layer.

    As workaround, you have to set all components of the grouped hole on the same level. You can use MicroStation Change Attributes tool to update the level of the grouped hole. That will resolved your issue.

    I will refer this unexpected behavior to internal instance. This is the best I can do for now.

    I hope that helps.

    Best Regards,
    Sebastien Lefrancois [Bentley]


    This is a test

    Answer Verified By: Krister Surell 

Reply
  • Hi,

    Yes. I reproduce the issue you’re reported here.

    As I said, in Map Manager, it will place Grouped Hole on default layer (you: GHOLE me:Level_0) when the Grouped Hole component elements are on different levels. If grouped hole components are all on the same level, map manager will recognize the level as a layer.

    As workaround, you have to set all components of the grouped hole on the same level. You can use MicroStation Change Attributes tool to update the level of the grouped hole. That will resolved your issue.

    I will refer this unexpected behavior to internal instance. This is the best I can do for now.

    I hope that helps.

    Best Regards,
    Sebastien Lefrancois [Bentley]


    This is a test

    Answer Verified By: Krister Surell 

Children