• State Not Answered
  • Replies 19 replies
  • Subscribers 59 subscribers
  • Views 9998 views
  • Users 0 members are here

[Map SS4] Corrupt DGN level table after SHP import

Oto
Offline

I have issue that importing SHP data in Map SS3, SS4 the resulted DGN file is not correct. Features are correctly mapped but the levels they are on are not marked as used. If executing DGN repair by Key-in:"mdl load verifydgn;verifydgn repair" then it shows long list of errors like "verifyElm_hdr error: no level entry element found for level 1483". Also Map sometimes crashes when trying to close this file. The levels are from dgnlib and are not in seed file I start with.

Parents
  • 0 Offline

    This is already logged as SR 7000132991 but not properly escalated.

    Run Level audit and the Level master tables are correct but auditing elements show lot of similar errors to this "ERROR: Invalid element levelid=1068"

    Also found out that if trying to import levels from dgnlib then the levels also are not correctly imported, it shows that linestyles are missing. Importing in MS there are no issues with the same dgnlib.


    Attached sample DGN, XFM,workspace(+DGNLIB) and sample SHP.ATIS-test.dgn ATIS-FullSampleSHP_data.zipATIS_XML.zip

  • 0 Offline in reply to Oto

    I've properly imported both .shp files into the a new created design file and into the provided design file as well. I've also ran and exported your .xml schema (atis-shp2xfm-new.xml) and did not have any problem to impor both shape files (points and polygone). At first sight, Bentley Map seems able to properly import the files. We need to search somewhere else.

    Sebastien Cote

    Regards

  • 0 Offline in reply to Oto
    See my workflow with the geo_example Bentley Map delivered workspace > screencast.com/.../AAVv23W00B

    Sebastien Cote

    Regards

  • 0 Offline in reply to sebastien.cote

    That is nice but not what is needed.

    Try to import using exported XFM Workspace(atis-shp2xfm-new.xml)  and map to XFM features.

  • 0 Offline in reply to Oto
    I get now, thanks for the video.

    However, all this is expected. shp feature instances are imported on the newly created level based on the criteria defined in your schema.

    Regards

    Sebastien Cote

    Regards

  • 0 Offline in reply to sebastien.cote
    So DGN corruption is expected?
    This is clearly a bug in Map because it doesn't correctly import elements in attached dgnlib levels only if they are already used in file
    and not only attached as level library. Bentley specialist for my SR was somehow unable to reproduce this issue. Can you please try once more using my workflow? Do you get the same DGN corruption and Map crash if try to close file afterwards?
  • 0 Offline in reply to Oto
    Oto. DGN corruption is indeed not expected. What I was saying is the level creation is expected, since you have defined a bunch of criteria in your schema. I've ran the keyin "mdl load verifydgn;verifydgn repair" and everything went well. Here is the MicroStation Message Center message > "verifyDgn verifying 476 elements in "D:\IOU\Map\2015\ATIS-test.dgn" for repair".

    Can you please rephrase the following > "it doesn't correctly import elements in attached dgnlib levels only if they are already used in file and not only attached as level library".

    With that being said, I don't think we have all what we need to properly troubleshoot and progress. What is the attached dgnlib you refer to ? Is it attached as a reference ? Defined to a configuration variable ? What content is attached as level library ?

    Here is a video of my workflow : screencast.com/.../x4OLFdwVLWbC. I did not get any crash afterwards.

    I would like to be able to reproduce, but I miss a few things I think.

    I'm also curious to know why you ran that verifydgn;verifydgn repair ? You wanted to do further tasks and it failed ?

    Sebastien Cote

    Regards

Reply
  • 0 Offline in reply to Oto
    Oto. DGN corruption is indeed not expected. What I was saying is the level creation is expected, since you have defined a bunch of criteria in your schema. I've ran the keyin "mdl load verifydgn;verifydgn repair" and everything went well. Here is the MicroStation Message Center message > "verifyDgn verifying 476 elements in "D:\IOU\Map\2015\ATIS-test.dgn" for repair".

    Can you please rephrase the following > "it doesn't correctly import elements in attached dgnlib levels only if they are already used in file and not only attached as level library".

    With that being said, I don't think we have all what we need to properly troubleshoot and progress. What is the attached dgnlib you refer to ? Is it attached as a reference ? Defined to a configuration variable ? What content is attached as level library ?

    Here is a video of my workflow : screencast.com/.../x4OLFdwVLWbC. I did not get any crash afterwards.

    I would like to be able to reproduce, but I miss a few things I think.

    I'm also curious to know why you ran that verifydgn;verifydgn repair ? You wanted to do further tasks and it failed ?

    Sebastien Cote

    Regards

Children
  • 0 Offline in reply to sebastien.cote
    Got it. ATIS.dgnlib is included in ATIS_XML.zip but you have to either copy it to exported workspace under project\dgnlib or fix XFM project so it takes it as template from your path(Base source dir) on GeoWorkspace export. Not sure if it supports relative path or variables.
    If the dgnlib is not provided then it works ok that is why it is hard to reproduce the issue.

    Regarding verifydgn it is just a test to verify that file is valid because otherwise no further tasks can be done and also program crashes on file close.
  • 0 Offline in reply to Oto
    Now I reproduce the "verifyElm_hdr error: no level entre...", but not the crash when I leave the application. Thanks a lot for the further details. Let me investigate it.

    Sebastien Cote

    Regards

  • 0 Offline in reply to sebastien.cote
    Can you also reproduce the issue when importing levels from dgnlib that some linestyles ar missing? There is no issue if I do it in Microstation, only Map.
  • 0 Offline in reply to Oto
    Sorry for this late reply. I've investigated it a little further, but there are still some "gaps". The only way I can reproduce it is when your schema AND the .dgnlib file are used. As soon as I remove one of them from the process, no warnings.

    For instance, the warning from the MicroStation Message Center says : verifyElm_hdr error: no level entry element found for level 1209.

    I've tried to find out where this 1209 level comes from and did not find it. All the leves from the arning message "talk" about four digits level name\number. I've looked into your GSA .xml schema criteria, in your .dgnlib file, in your design file, and there is nothing linked to 1209 level in there. I've reviwed as well the .shp and there is data only linked to ATIS_CODE column. And again, we don't talk about 4 digits values.

    Any idea regarding that ?

    Otherwise, we might need development to take a closer look.

    Not sure the warning message is not expected here. It seems it tries to find something on the level, but the level is empty. So it warns it.

    Sebastien Cote

    Regards

  • 0 Offline in reply to sebastien.cote

    The problem is simple. Bentley Map does not import levels if they are linked from DGNLIB. This is not normal behavior as normally in Microstation if I set a dgnlib level as active and draw new elements using drawing tools then the level is automatically added to active DGN file level table and marked as used. The level number you see comes from autonumbering(CAPABILITY_LEVELS_USE_AUTO_GENERATED_NUMBERS) . If I import levels from dgnlib using Microstation(because there is another issue if importing in Map) then the import works ok. Also see that only level with name 1000000001 imports correctly because it is not defined in DGNLIB and so doesn't make a conflict.

Communities
Support and Services
Training and Learning
Social Media