Ronald Brys's Activities

OpenRoads Designer CE R3

Ronald Brys — Mon, 15 Oct 2018 17:06:21 GMT

I'm importing a ALG file from InRoads SS2. Although the feature definitions exist in ORD CE the geometry styles do not map between versions. Imported geometry lands on level 'default'. User error or software limitation?

Thanks, Ron

Ask A Question I

Mon, 15 Oct 2018 03:17:32 GMT

Ask a question in a forum.

Ask A Question II

Mon, 15 Oct 2018 07:21:08 GMT

Ask 10 questions in a forum.

Corridor modeling in Power GEOPAK SS2 ddb file error

Ronald Brys — Wed, 08 Jan 2014 01:11:08 GMT

When selecting a ddb file for conversion to an xin file for use in corridor modeler, an error dialog states the file is not able to be converted. However a xin file is created in the rddbs folder but no drafting standards are available. I've tried reselecting the 'job' file, restarting, rebooting and reinstalling the software to no avail. I was trying to convert the default_styles.ddb file provided with the software.Have also tried other ddb files, swapping out the xin file that is created in the rddbs folder. The results are the same in that no drafting standards are available for importing geometry or running roadway designer. Any ideas?

Thanks, Ron

OpenRoads Survey - Custom operations

Ronald Brys — Tue, 13 May 2014 14:16:54 GMT

Power InRoads 08.11.09.674

When using a legacy XIN file and OpenRoads, cells placed through custom operations don't scale when choosing a different drawing (model) scale. However they do if placed as a function of the named symbology. Also a rotation attribute is not applied. Is there a solution to these issues?

Thanks, Ron

Open Roads and multiple file use.

Ronald Brys — Tue, 02 Feb 2016 01:20:25 GMT

The best practices information I've found suggest using different dgn files to seperate design data.

However if mainline and side road horizontal and vertical geometry
is stored in separate dgn files, it seems you lose the ability to project ‘profile
intersection points’ between files. Is
this correct or is there a workaround?

This also seems true for civil cells. The ability to select
reference elements in separate dgn files does not seem feasible. Workaround?

Thanks, Ron

OpenRoads SS4 Cross Sections

Ronald Brys — Wed, 13 May 2015 16:02:35 GMT

When generating dynamic or graphic cross sections, template vertices are being automatically annotated. Changing the design stage of the corridor has no impact. The display of crossing features are turned of in both the default view and in the 3D view. All feature definitions are defined as 'native'. Whether the native style has surface>cross section crossing points or annotation on or off has no impact.

As long as I'm at it, why doesn't existing ground display even though it's the 'active' terrain element? Cut/fill slopes terminate at the existing ground......

How can this be controlled? Image attached.

Thanks!

OpenRoads 4

Ronald Brys — Wed, 28 Jan 2015 17:30:58 GMT

See image for what I'm trying to 'cleanup'. Using SS4

Looking for direction on:

Defining or adding (in SS2 terms) Maximum Segment Length or Point Density Interval to a linear element in a Terrain Element. Scenario - added a line to the bottom of a sed basin to introduce a drain. Did so by using a filter Create Terrain by Text Interpolation. Now I only have the begin and end of the imported line. I wish to add additional triangle vertices along the line.
Adding a single spot elevation to a terrain element. Edit terrain>Insert vertex will work but requires working in a 3D model, setting display depth and active depth. It's cumbersome. There has to be an easy way to add specific points at a defined (key-in) elevation...
Is there something that replaces importing a numerical text string that uses the text justification for location and reads the characters for the elevation - without a connecting line?
Is there a command/workflow similar to the InRoads command Generate Transverse Features?

Civil Cell - Corridors not clipping

Ronald Brys — Thu, 02 Jul 2015 17:19:58 GMT

Any ideas on why corridors do not clip correctly when using a civil cell? I'm using the 'Basic T' civil cell provided with SS3. The intersecting corridors are using the same template/end condition as the civil cell. I've gotten it to work just fine in the past but now it only partially works. See included image.

OpenRoads SS4 Cross Sections

Ronald Brys — Wed, 13 May 2015 18:41:42 GMT

When generating dynamic or graphic cross sections template vertices are being automatically annotated. The display of crossing features are turned of in both the default view and in the 3D view. All feature definitions are defined as 'native'. Whether the native style has surface>cross section crossing points or annotation on or off has no impact.

As long as I'm at it, why doesn't existing ground display even though it's the 'active' terrain element? Cut/fill slopes terminate at the existing ground......

How can this be controlled? Image attached.

Thanks!

Design input report - Templates SS4

Ronald Brys — Thu, 29 Jan 2015 20:55:45 GMT

This is similar to Adams concern.

If a template is edited in the corridor definition, other than running an XML report, is there any other way to determine if you are using 'stock' templates or modified templates? When reviewing Corridor Objects > Templates, there should be something indicating template status. ie the old itl or ird notation in InRoads when reviewing corridor definitions. Synchronizing with the template library can cause unanticipated results.

Civil Cell is invalid and cannot be placed

Ronald Brys — Fri, 16 Jan 2015 20:15:26 GMT

Using SS4

I successfully placed a civil cell in my design. I then deleted it using the fly-out menu from the civil cell.

Upon returning to the drawing and trying to place another civil cell I get the following dialog/message (which will not stay closed) and then Power InRoads has to be closed using task manager..

"Civil Cell is invalid and cannot be placed"

Any Ideas on how to resolve this? No evidence of the civil cell shows up in Project Explorer. I opened/closed/compressed the file, etc.

Thanks, Ron