I might be doing this wrong. You can see in the first point I have my name and description. After creating the point the dialog comes back as the next point to create. Why has the point number been reset, how about automatically filling this in with next point number. And why has the description changed? How about leaving that the same too? I might have the same description for a "2' O/S SW" for 20 points.
So I have to retype both every time?! In Civil 3D it will step the number and leave the description. All I have to do is type the elevation, click, repeat. That seems almost to easy. Plus it will keep a list in the background of the descriptions and you can up and down arrow to scroll through the ones used in that session, very convenient.
I hope someone can show me a better workflow because this is ludicrous.
Does your feature definition have a seed name?
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Could I change something in here to get the desired results?
If I just what to work in my design file I have to place a temporary dummy point. Then open the standards and tree to the Misc_Point and change the name seed to 1. Then you are correct it will increment. It doesn't fill in the dialog box on the next point but it's slightly better. The description doesn't hold. But I guess I could change that in the Standards properties when I need it switch. It is clumsy but it's better than a poke in the eye. Thanks for the help. As a civil 3d user you understand how it's way easy in that program. Maybe Bentley can improve on this in the future. This is a real world problem that your average user wouldn't know how to fix. Imagine filling in those boxes for 200 pavement offsets.
InRoads is 100 times better working with COGO than ORD, but I hear that Bentley is going to be working on their COGO-based tools in upcoming versions of ORD. ... so I have my fingers crossed.
That would be great. But as you know, most of the ORD users are for DOT's and have to stay within the limitations of the file format.
I know, but InRoads was also a DOT-centric application and it had pretty strong COGO capabilities.
And, if you have a support contract, you can request an installation file for a stand-alone copy of Cogo Classic, which is the ICS Cogo of InRoads.
We are continuing to deploy it for people who need traditional COGO capabilities.
I wonder if they have one for Geopak, that's what I'm familiar with. Do these work in the new ORD file formats?
For Cogo Classic, it can create an ALG which can be imported as alignments and cogo points. I do not know if they support GEOPAK Cogo outside of MicroStation. The ALG file is basically the InRoads version of the GPJ file.
Cogo Classic was basically a port of their Mainframe Cogo program - ICS. And much of it was built into InRoads, but they always supplied Cogo Classic until Ss4 or Ss10.