What are the capabilities of COGO points for Open Roads?

I recently completed a task that took advantage of COGO points in Power InRoads Ss2. I have found a myriad of traditional and non-traditional uses for COGO Points over the years.

Over time, as I understand it, Open Roads will incorporate more and more of the native Civil/Site tools until at some point, there will only be Open Roads. Will Points in Open Roads have all of the capabilities of COGO Points in the native tools?

Believe it or not, we still find uses for ICS input files. And I recently needed to filter my points with an XML Report based upon a Fence. Will these continue to be available?

I guess, if there were no plans for this, I'd like to make a motion that the capabilities of traditional COGO and the native XML Reports are carried forward into Open Roads. Please feel free to second the motion if you agree.

  • I'll second that!! I LOVE COGO Points. ...really ...I do. But COGO points and I have a lot of history. And I work with a number of others that feel the same way. I'd miss them if they go, and agree that the legacy usage has to be retained.
    Civilly yours,
    The Zen Dude (also known as "Mark")
    Civil Software Guru & Philosopher
    InRoads User since its birth in the 80's
    OpenRoads Documentation / Training / Support
    Zen Engineering, Owner
  • The best way to make sure your needed workflows are covered is to describe specific use cases. A statement such as "I need Openroads points to do everything that InRoads cogo points can do" is not really very helpful because we have no idea what sorts of creative uses you might have devised.

    For example, you mention that you have uses for ICS files. What problems are you solving by ICS files?

    Report based on a fence? already there, but perhaps you have specific workflows that are not working?

    You get the idea. If you can describe your needs in the form of a use case, workflow or problem then it is easier for us to determine a solution to be developed or describe a solution already in place.

    It is also important to keep in mind that OpenRoads is a new toolset with new capabilities (such as 3D and preservation of design intent). Thus, it is very often the case that a more efficient solution is possible but is different than your traditional workflow.

    Robert Garrett
    Senior Product Engineer
    Bentley Systems Inc.

  • Absolutely AGREE.....I used cogo point for designing special ditches. I know end conditions can solve what I am about to explain but here goes. This solution reverts back to the days when we were using decision tables....V8.1 - V8.5.

    1.) I would run the modeler and create cross-sections
    2.) Using Microstation tools (line by active angle) I would create lines to represent my ditch bottoms. I had created settings groups for active angles to relate to the slopes that I wanted to create.
    3.) Once the ditch bottoms were created, I used the drafting tools to find the ditch bottom, station, offset and elevations.
    4.) Then I would store cogo points in a 3d file and chain up the points. (I suppose you could have wrote a TIW, but keying them and storing for me was quicker)
    5.) Import the linework as a Horizontal and Vertical alignment.
    6.) In the point controls I would target the ditch bottom alignment in the end condition.

    This has been my preferred method. I am sure there are other ones out there. But, this is one way that I have used cogo points.

    Another use that I had for them was for survey field edits. I would be given an ascii or text file and after some editing I used the TIW to store and display the points in a 3d file. I would then update the mapping DTM using these points.

    Very handy and useful command to make our life's simple in the design world.

    Joe Lukovits

    User Since TDP in the 80's,

    Vax based Unix Workstations - Interpro32,

    from the Intergraph Corp.



    • Sometimes we need to generate list of points and sometimes the client specifies a particular order after the fact.
      • So we start with our original buffer and create an XML report to open in Excel where we can reorganize the points to meet the order the client has asked. We will build a series of ICS input lines to recreate the stored points using formulas in Excel.
    • We also sometimes use custom XML Reports that create new ICS input files to make edits that are difficult to do using the graphic tools.
      • I've used ICS files to combine multiple horizontal alignments into a single alignment and then use an ICS file to rebuild the vertical alignment for the combined horizontal alignment that contains a likewise combined vertical alignment from the two original horizontal  alignments.
    • I've even use ICS files as a sort of spacial database.
      • Points were named using information that was needed as part of a bulk label. The Styles were created to control the display of points as they were plotted, sometimes using "as defined" and sometimes with an override. The descriptions were also used for yet more information that also was part of a needed label.
      • In this process, we took spreadsheet data to build ICS batch files to bulk load the data. The original data was provided as a table in a PDF so we really needed to call out all the stops.
    • One of our local jurisdictions is very picky about how you recreate properties and right of way information.
      • They will often question the "intent" of a particular point or line - that is, how did you determine this location. Using ICS is almost the only way to be able to answer their questions in a manner that they can review. And if they disagree with some segment of the process, you can edit the ICS file to match their request and rerun the process.

    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
  • Regression Analysis uses Cogo points as well. I have used this a couple times to establish existing alignments.

    Joe Lukovits

    User Since TDP in the 80's,

    Vax based Unix Workstations - Interpro32,

    from the Intergraph Corp.