Hallo,
while migrating to ORD I've found some questions I havn't found answers or help. So I would like to ask in the community.
1. I've found that other users asked for control codes missed from InRoads, for me especially the CLSRECT and the EXTARC. It's for the compatibility of older surveys, but it's also not so easy to locate the centerpoint of an 10m-circle to use the CR- or CD-Code - in this case the use of 3 or more points to define the circle is more easy and mor accurate. Is there a new statement from Bentley to this requests? I'm using ORD 2019.1.
2. In the Decorations I can switch the Names, Elevations, Codes... - but how can I switch off or change the display of the points on linear features?
3. In InRoads I used the custom operations to annotate points by properties like Elevation, Name or attributes. In ORD I defined the "normal" annotations using existing properties, but havn't found a way to annotate with calculated or conditioned values: for a tree I have 2 attributes - diameter and type, but they are not collected in each case. So when the type is missed, I don't want to display the prefix "Type=". For a manhole i annotate always the top elevation, but sometimes we collect a special manhole name and the depth. I also want to display only existing information, but from Elevation and depth I want to calculate the height of the manhole ground. Is it only possible to do so with VBA annotations? And if so, where can I find information and examples for this?
Thank you for helping!
Best regards
Steffen Römer
GEOKON
is there no one to help me? If there's no user with the knowledge - where's Bentley with the helping hand for migration to Connect Edition?
By this time and with this kind of software and help I can't use ORD for production purposes.
So please give me some hints, Bentley.
Hello Steffen. I think your ahead of the rest of us in the survey community. I know in my area there is no local support amongst the surveyors who will eventually be forced into ORD. With that being said I hope you can help some of us who are migrating into ORD over the next 6 months.
It can be a roller coaster ride being at the tip of the spear with this technology. Hang in there more are coming!
Cliff
Sorry that I did not see your post until today. I was on vacation for a week and when I got back we had a very busy (last) week with Bentley on Site to go over some plans for migrating to ORD.
1. CLSRECT is similar to CloseShape and can probably be remapped, but in some cases the results will not be satisfactory.ExtARC is gone. You can use the FrontBack code (similar to the +D) to add to the shot's slope distance to place it in the center of the circular object. I actually plan to test using +D, +H or +O as a code for the FrontBack, UpDown and LeftRight codes, but have not gotten around to it.
2. I do not believe you can toggle off specific decorators, unless you toggle off the attached features.
3. there is an MVBA called SmartObjects.mvba delivered with the product. It has functional examples of VBA macros that can be attached to a Survey Feature along with example command parameters. There is also a WIKI page with example files and a video. The Video only shows how to create a 3D pipe from pipe inverts but we have it reading attributes and acting upon those values. We were even able to test for inconsistent attribute values and make the labels red as a flag that there are two points on a single figure that have conflicting attribute values. It knows the difference between linear and point features and can do different things for linear annotation than it does for point annotation.
The "built-in" label survey capability can do a lot of this, but does not have any error checking capabilities that the VBA macro code does. The downside of the VBA Macros is it slows down processing if you do a lot of it. We were still working on our Ss4 workspace where there are no other labeling options so we tried to replicate most of what we used to do with custom codes.
One option for item 2. is to use the basic survey Annotation instead of the decorators and to segregate those labels to enough levels that you can isolate points from linear decorators.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
We ran through the issue of CLSRECT not being available any loner. As you state its an issue with bringing in old surveys. There needs to be an easy way for that code to be mapped to close shape.
Regarding the results of close shape. how do you know what is correct for an assumed point? The command does give you a different result than in the past but who is to say it is right or wrong. Here is an example of closing a shape, all 4 points are possibly wrong or correct.
~HTH
John.
yep
Hallo John, I think it's my part as the surveyor to say the image is right or not. There is no documetation on how InRoads calculates the point. I some times - if I don't like the result - i calculate the width of the desired rectangle with the stakeout command and change the code in the RECT and the found width. So - and with your image in mind - I can understand Bentley for removing the code and we don't use it anymore - my question was only for older datasets. But in my opinion it was point 3 that was calculated.
Steffen Roemer