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.