Open Roads Survey for InRoads Survey Users Guide

This is a desperately needed manual! The more I play with this, the more I am convinced that I will never switch to Open Roads!

Can you hear my frustration? I'm going on a rant. You can join me or ignore me. I just need to vent a little.

Now I am getting no linework and all of my points are assigned Default as their feature. I've tried bringing in our standard TDS RAW files, or our already save FWD files. What I get is crap!

When I was getting lines, I we having issues with JNC or DASH "-" coding, along with dual point coding. Dash coding is for an Electric Pole with a Guy Wire. You shoot the pole with EP and the Guy Wire with GUY-EP and you get a line connecting the two and the Guy Wire cell rotates to align with the line. Alternatively, you could use one of the following:

  • EP-GUY on the pole
  • EP JNC GUY on the pole or
  • GUY JNC EP on the guy wire

Since I am not getting my point codes nor my ST codes recognized, a dual code is light years away.

I have found no other coding method that worked as well as InRoads Survey, and was pleasantly surprised to see that Civil 3D can now be configured to recognize most of InRoads codes, including dual coding. I feel like Open Roads Survey is a step in the wrong direction.

When I link my XIN, why doesn't the software automatically also use my control codes? And why are the buried so deep into the software. And why is the help on many of these settings no help?

For Example, what is a "Description Separator"?

With InRoads, we use ALPHA CODES and CONTROL CODES. And every other bit of info is entered as Attributes, which are not inline with the other codes. All I need is for it to read alpha codes and control codes for each point and then read the attributes associated with the point.

I still cannot believe that we are expected to have no alpha codes that "contain" linking codes? Who thought that was a good idea.

Parents
  • OK, now that it's off my chest...

    I edited the mysterious "Description Separator" adding a dash into the field and tried one more time to import my FWD.

    Linework! Dual Codes! Attributes read and used for labels.

    I still need my original point coding to be exportable.

    The current InRoads Survey XML report is an essential part of our workflow!

    One more thing. My fence line is using the proper feature linestyles. But my pipe inverts are using LC=3 intsead of the various styles in my XIN file. We shoot pipe inverts from inlet to inlet and get 3D breaklines that can show up on cross sections and profiles, but for plan view, plot double lines that are the width of the pipe diameter. Why is is not seeing my XIN linecode for these?


    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
Reply
  • OK, now that it's off my chest...

    I edited the mysterious "Description Separator" adding a dash into the field and tried one more time to import my FWD.

    Linework! Dual Codes! Attributes read and used for labels.

    I still need my original point coding to be exportable.

    The current InRoads Survey XML report is an essential part of our workflow!

    One more thing. My fence line is using the proper feature linestyles. But my pipe inverts are using LC=3 intsead of the various styles in my XIN file. We shoot pipe inverts from inlet to inlet and get 3D breaklines that can show up on cross sections and profiles, but for plan view, plot double lines that are the width of the pipe diameter. Why is is not seeing my XIN linecode for these?


    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
Children