[Map SS4] Corrupt DGN level table after SHP import

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 Reply Children
  • That is nice but not what is needed.

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

  • 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

  • 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?
  • 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

  • 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.