InRoads Survey XM w/ AutoCAD & bylayer linestyles

Running InRoads 8.9.2.16 inside of AutoCAD 2008. When writing Survey Data to Graphics, the linework is taking on the bylayer linestyles instead of using the bylayer settings. If I set a linestyle, it uses that linestyle, even if the layer's linestyle is different. But when I set it to bylayer, it writes ti to the file with a forced linestyle instead of bylayer.

The XIN originated in a MicroStation session, if that is significant. 

I also noticed there is no Named Symbology tools in the AutoCAD world. Can I export and import named symbologies while in MicroStation and have the end result work OK in AutoCAD? It looks like the global named symbology tool writes some information that is only used by MicroStation and does not write some information that is used by AutoCAD.

As I need to make bulk edits, the import export option seems to be the only viable alternative.

Can I also get an explanation of which fields contain different data depending upon the platform used? I'm very used to working with XML data in its native format and could use a text editor if necessary.

PS - The CADDCOP is now hanging his hat at a new firm. The economic downturn resulted in only a minor hiccup in my career. 

Parents Reply Children
  • Jason,

    Thanks for stepping in. I have a few other questions... 

    Is that a priority build or a pending SP?

    Below are some questions from my original post that I could really use answers to. But first, let me touch on a tool related to those questions. That tool is the import/export Named Symbology tool. I must admit that it is extremely unstable and sometimes unpredictable. Today, I tried importing a verbose and non-verbose single file, set to "replace duplicates" and both resulted in Exception errors. At my last employer, I had equally mixed results, but occasionally succeded in importing. When it did work, it sometimes created XXX_1,XXX _2 duplicates and other times did not. This would occur it set to rename duplicates even though I had deleted all original named symbologies. Also, it did not occur on every named symbologies. The ones that it did occur on, resulted in only default, only plan, only profile and/or only cross section symbology for each name, as though they were duplicates.

    Here are my still unanswered questions from my original post:

    I also noticed there is no Named Symbology tools when running InRoads in the AutoCAD world. Can I export and import named symbologies while in MicroStation and have the end result work OK in AutoCAD?

    It looks like the global named symbology tool writes some information that is only used by MicroStation and does not write some information that is used by AutoCAD.

    As I need to make bulk edits, the import export option seems to be the only viable alternative.

    Can I also get an explanation of which fields contain different data depending upon the platform used?

    I'm very used to working with XML data in its native format and could use a text editor if necessary.

    Thanks.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • InRoads Group V08.09.03.06 is basically a service pack.  They are no longer referred to as service packs because you can now install them by themselves without requiring previous builds as was the case in older versions (e.g. InRoads V08.05.00.00 had to be installed before a service pack was installed).  In your case, V08.09.03.06 will replace your V08.09.02.16 installation.

    If you are having problems with the Named Symbology Tools, then you should log an issue with support:  http://appsnet.bentley.com/srmanager/addcall.aspx 

    You are correct.  The Named Symbology Tools are not available when AutoCAD is the CAD platform.  You should not use the same XIN file in both MicroStation and AutoCAD.  The Named Symbology Tools should not be used to edit XIN files to be used within AutoCAD.  If you feel these tools should be added, please log a change request with support from the link above. 

     I hope this helps.

    Jason Smithey