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:
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.
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 Maryland DOT - State Highway Administration User Communities Page
Unknown said: And why is the help on many of these settings no help?
And why is the help on many of these settings no help?
Because they want you to buy a training subscription.
[/quote]
That maybe true and sad for this Bentley company!
But a piece of software is not complete as long there are missing's within the documentation! So in my thoughts I will use OpenRoads when it is fully complete, I would not have time to play around.
Thanks to you guy's testing it out! (mmmh... isn't testing a process of software development?)
Regards
Frank
since 1985: GIS, CAD, Engineering (Civil) Senior Consultant : [Autodesk Civil 3D , Esri ArcGIS, VertiGIS: in previous days : Bentley MS V4 - V8i, GeoGraphics, Bentley Map V8i, InRoads, HHK Geograf, IBr DAVID] : Dev: [C, C++, .NET, Java, SQL, FORTRAN, UML][direct quote by: http://en.wikipedia.org/wiki/Helmut_Schmidt]: "Wer Kritik übel nimmt, hat etwas zu verbergen"Wer Grammatik- und/oder Rechtschreibfehler findet, der darf sie behalten :-)
Spent some more time with this over the weekend.
Is there issues with ALPHA CODES containing other ALPHA CODES?
Our main client provided all of our alpha codes. They have a PINV along with a PINVA thru PINVQ. Feature name = ALPHA CODE.
If I link only survey XIN, I only get PINV. If I change PINV to PINVX, other PINV alpha codes begin to appear.
If I link Survey and then Civil (same XIN - is that a problem too?) I get all of the other PINV[A-Q] but they are not set to Survey in their properties.
I also played with my cells - made a new copy of my cell library and made them all annotation cells. But linestyles may prove to be an issue.
How can I get my "do not scale" linestyles (which are defined as physical) to not scale with annotation scale when I set my model to use annotation scale for linestyle scale factor? In the XIN file, we leave the scale box unchecked and the InRoads Scale factors (survey and regular) do not impact them. Only those with a scale factor set to 1 in the XIN get scaled. Can I get the OpenRoads created linestyles to also work like this?
I’m also having major issues with this software. I’ve been using geopak survey for 15 years & Microstation for almost 20.
I cannot get this software to do anything close to what we currently do with the older software after playing around with Data Acquisition for several hours.
I think there is a reason that this software is kind of buried deep down. I will look at it again next release.