InRoads SS2 Corridor Point controls interfere with targeted corridor surface

I am having a strange problem applying point controls using Corridor Point mode for a project in InRoads SS2. I have a roadway alignment and corresponding corridor in an .ird file. I will call this corridor in the .ird "Main_Street". In the same .ird file, I have another corridor that follows the same aforementioned roadway alignment. I will call this other corridor "Main_Street_staging". I plan to use the corridor "Main_Street_staging" to create intermediate construction staging cross-sections for the final corridor "Main_Street". To do this, I thought it would be useful to create point controls in the "Main_Street_staging" corridor which reference Corridor Points in the "Main_Street" corridor. That way, if changes are made in the "Main_Street" corridor, then they would be automatically updated in the relevant parts of the "Main_Street_staging" corridor that reference "Main Street" without having to replicate those changes in the related corridor. So far so good.

The problem I am experiencing is this: now that I have set up these point controls in my "Main_Street_staging" corridor, the original "Main_Street" corridor no longer generates a usable surface. At a certain station, the "Main Street" corridor looks like this in the Roadway Designer window:

View in modeler

...but it's cross-section at the same station looks like this after creating a surface:

Cross-section from surface

If you think they look nothing like one another, we are in agreement. After setting up the Corridor Point controls in the "Main_Street_staging" corridor, all the cross-sections in the targeted "Main_Street" corridor now appear as variations on the theme of a diagonal white line throughout the corridor. I have read warnings about avoiding recursive targeting; however, the "Main_Street" corridor does not target anything in the "Main_Street_staging" corridor, so I don't think there are any opportunities for recursion issues here.

The quickest way I found to fix the problems with the surface created from the "Main_Street" corridor is to delete the "Main_Street_staging" corridor containing the point controls targeting the Corridor Points in the "Main Street" corridor. Upon deleting the "Main_Street_staging" corridor, the surface generated from the "Main_Street" corridor looks fine. However, this isn't my preferred solution, as I still need to have a "Main_Street_staging" corridor, too. Is this a known bug? Any help is greatly appreciated.

  • Are you creating only one surface at a time?

    You can create a single combined surface or create separate surfaces at one time or create a surface from a single corridor at a time.

    Are the point names and style consistent along the entire corridor?

    I worked on a project, after inheriting it from others, where many template drops reused point names in different locations within each template drop and as a result, in some locations, they were a subgrade feature while in others, they were finish grade. Needles to say, the surfaces were not usable.

    Are the features written to the DTM at their correct elevations but their properties set to Do Not Triangulate?

    Sometimes you can change their properties and fix the issue.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration
    Maryland DOT - State Highway Administration User Communities Page

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • Hi Chuck, thanks for your reply. I am creating one surface from a single corridor. And yes, the point names and styles are consistent. The features are not being properly written to the DTM. Most do not show up at all.

    The only two things I've found that fix the issue are (1) delete the other corridor in the .ird that is using the Corridor Point controls, or (2) don't delete the other corridor, but delete all the point controls set to Corridor Point type (disabling the point controls is not enough, they have to be deleted).