I am running SUDA (Power Geopak SS4) and need to design an inlet that has a depth of 2 ft. Right now the inlet when placed defaults to like 2.75 ft. and we can't change it to be anything less. Is there something we are missing in the set up of the Node to be able to change that depth to something less?
↧
Node (Inlet) Minimum Depth
↧
ORD 2019 R2 Refresh – Problem with Transform Tool on Vertical Complex
Hi, when using Transform Tool on PI based vertical complex element (comprising tangents and curves between elements) with copy option un-checked (to basically move the alignment) the resultant complex element changes last curve to “curve from element” and extends last tangent back to PI towards the curve. This way integrity of the vertical alignment is lost and subsequent changes to the curve results in non-tangential connection. This problem occurs using all three methods: Cursor Points, Deltas and Points.
Below is sample original complex:
And the following is the complex after transformation:
In order to fix the alignment dropping complex, deleting the affected curve and re-creating the curve as “curve between elements” and re-complexing is required (with all its consequences).
Has anybody experienced this problem?
We consider transform tools very useful but this problem require additional, unnecessary work to fix alignment. Note, one use of transform tool can be to simplify alignment in such way that gradients of associated tangents remain fixed when one tangent is changed by manipulators (moved, gradient changed etc.) – unlike using Simplify Geometry tool.
Regards,
Mariusz
↧
↧
Overlay/striping not show the style when surface created
Hi there.
I have a issue with the overlay/striping component not showing the style when created as surface.
When I look at it in my Roadway designer i have no problem viewing the overlay/stripping with the correct style.
As soon I create a surface of the overlay/striping component it dosent shows with the correct style. When i look into my "Name and symbology" everythings seems to be setup correct.
The component is placed on the correct level, just not shows the correct style.
When i try to "drop element" and set the single mesh faces ByLevel, it changes the color to match the correct style.
I am working on Power Rail Track SS2.
Does anyone have had simular issues, and does anyone have a solution for this issue?
↧
Create terrain by text interpolation not work
I created a 2d file where I placed heights using the text tool.
Then I attach this 2d file to 3d model.
When I try to create a terrain model, nothing happens.
I tried exactly as per the instructions:
https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/9881/video-import-text-as-spot-elevations-to-create-a-terrain-model
I am posting my DGN file and asking for help
https://1drv.ms/u/s!AoKLTsHic9oZiSHoczmtQ3funPgH?e=8TW1OH
↧
DTM Import error Inroads ir081109878
I'm having an issue where we import a DTM and the surface generated is incorrect one way correct another.
Importing via Terrain Model it creates misc / incorrect contours. It almost looks like there is extra triangles being generated that its causing extra contours.
Importing via legacy InRoads it generates the surface fine.
Has anyone ever had an issue when importing one way vs the other gave different outcomes?
The contour intervals were both set at 1' intervals.
↧
↧
Limiting slope on through lane while curb profile is variable
I can't help but feel there is a simple solution for this but here I am, in need of the great wisdom of the community here.
I'm trying to get my road shoulder slope to vary while the slope from my centerline to the edge of travel lane fixed at 2%, while my gutter inslope from edge of pavement to the gutter flowline is fixed at 6%. A vertical point control will be placed on the flowline so the curb will move vertically depending on the curb profile.
The road shoulder should never be flatter than the slope of the through lane. If the road shoulder needs to be flatter than 2%, the through lane will match the road shoulder slope.
The two not-really-solutions I could think of are:
1) Setting a zero vector-offset between the centerline and the edge of pavement but my through lane slope will be matching the road shoulder slope when it is steeper than 2%.
2) Setting a slope constraint of 2% from the centerline for the through lane but the shoulder could be flatter than 2% and cause a dip.
How do I get the shoulder slope to vary so it is 2% or steeper when the curb profile is low enough, and also able keep the through lane slope to match the shoulder slope whenever it gets flatter than 2%?
Thanks for any help in advance!
↧
OpenRoads Concept Station Question: What's the difference between "Ramp(Left Origin)" and "Ramp (Right Origin)"?
Trying to add ramp from freeway to minor road, don't know what is the difference between these two option: ramp (left origin) and ramp (right origin)
Could anyone help to answer my question as soon as possible?
See attached screen shot.
Thanks.
↧
Profile Sets
When I create profiles in In-Roads everything works great, I save the project and the alignment. When I close In-Roads and open my files again the profile sets are never saved thus I can't modify the profiles that I created nor add points to profiles etc. Is there a setting that I am missing or how do I get the profile sets to save?
↧
[OR SS4 .878] Issue with Annotate Cross Section < Create Cross Sections < Process Corridor, and Feature Definitions > Cross Sections > Element Template
Practical question: How do I get rid of these crossing features that I no longer want to show up in my cross sections and my annotation list?
Allow me to trace the problem back.
Primarily, when using Annotate Cross Sections, I want my Crossing Features list to be populated only by those features that I want to annotate so that I can simply click All, instead of taking a lot of time to select only those features that I want to annotate. It's not relevant to the solution, but just so you know why I'd rather do this: I have a huge number of surface and subgrade features, and I want to annotate only surface features, and even then I don't want to annotate some surface features.
This means, in part, that for the points I do not want to annotate, I need to not have an "X" where the feature crosses a generated cross section. (I speculate that I also need to not have a point where the feature crosses a generated cross section, but that's moot for me at the moment, since I see no such points in my set of cross sections: I confirmed this by selecting everything in the cross section and assured myself that there are only non-zero line segments, characters, and cells.)
This means that I need to be sure that, via Project Standards and Element Information, the element template field for cross sections needs to (1) be blank, or (2) be supplied with a selection that does not place a character or cell under Point Settings. For all the feature definitions that I don't want to show up, I have made sure that in the file in which these features are created, both native and element template is blank under cross sections. (I've also made sure that the Create 3D Automatically is disabled as well, though again, that's moot for me.)
From the above, I should be confident that no X will be created in the cross sections, but there they are. Now, I recently revised the element template for those points that I do want to show up. To test, I revised the element template so that the features that I do want to show up in the cross section annotation list will now display a distinct circular cell instead of the character 'X'. After I reprocess the corridor, we should guess that any X that shows up in the cross sections at this time should be zombie elements. I find that this is true: The Xs that I see in the cross sections are representing those features that were already created in previous corridor reprocessing.
Fundamental question: How do I refresh the corridor's file to the point that these old features are no longer constructed in cross-section space with a template that it is no longer associated with?
I tried deleting the offending features from the corridor file's 3D space, but that was unsuccessful; I cannot delete any of the 3D features from the corridor's 3D space. What else can be done here?
↧
↧
[OR SS4 .878] Element Templates are honored in one corridor's dynamic cross sections but not another corridor's
In one single file I have two corridors (note: this is not just two template drops within one corridor), both corridors along different segments of the roadway separated by a bridge.
Some of my feature definitions use one common element template to place a circular cell where features of that definition cross the cross section. I have made sure I reprocessed both corridors since making the change.
One of these corridors honors that element template and places a circular cell as desired. The other does not honor that template. Why not?
↧
Alignment File Crashes when trying to remove vertical inflection point
I am trying to remove a VPI from my complex verticle alignment. When I use element selection - delete vertex, it crashes my system. Is there another way to delete VPI points out of verticle alignemt?
↧
ORD Second Station / Chainage in Profile Frame
Good day
Need to add two different station / Chainage values on profiles.
Unable to find a option to add Row definition to set up a point targeting a station on a different profile.
Projecting a second alignment onto the profile do not allow a point definition to target a point on a profile, already added in the active profile.
↧
PowerGEOPAK SS4 Scanning Models upon exiting file
Hello, I am using PowerGEOPAK SS4 and my dgn file has about 15 models so it takes forever to close a file (at least 5-10 minutes) because of the Status "Scanning Model: x" dialogue box that goes through every single model.
Does anyone have the same issue/ any workarounds?
Thanks!
Samy
↧
↧
ORD WORKSPACE ISSUE
I have created the Workspace for my Company in ORD connect edition, but it is not showing in the ORD explorer in the right side (Openroads Standards) in Libraries, DGN and feature symbologies. Please see below snap shots.Can Any one has idea why it is not showing?
↧
ORD WORKSPACE ISSUE
have created the Workspace for my Company in ORD connect edition, but features and symbologies are not showing in the ORD explorer in the right side (Openroads Standards) in Libraries, DGN and feature symbologies. Please see below snap shots.Can Any one has idea why it is not showing?
↧
Open Roads Designer Connect Edition
I just Downloaded Open Roads, I have some sheets that were done in Micro station V8i Select Series 4 and when I open them in Open Roads Designer Connect Edition it states that V8I Select Series 4 is not supported in Open Roads Designer its read only open as read only.
And when I do a save as its still read only
Is there something that I need to download 
↧
Self Intersecting Alignment and Plan Production
I am currently working on a large interchange project and am experiencing some weird results when generating plan named boundaries for a self intersecting alignment (e.g. cloverleaf). The left alignment in the image below is the subject geometry. I'm using a client supplied template and don't really understand if this is a defect in the OpenRoads platform or an issue with the way the geometry for the alignment was constructed. Seed scale and overlap settings make little difference. The named boundary element placement goes out of whack at the point of self-intersection and does not follow the stationing sequence. I am a new user to OpenRoads, but have a heavy background in Civil3D. Any assist that can be provided to troubleshoot this would be greatly appreciated.
↧
↧
SUE/SUDA Workspace error
I'm running Release 1, Update 7 - Ver. 10.07.00.56
When I try to place a node in my file, ORD prompts me it is going to create the model and then I get this error. I have checked the SUDA_SEED_FILE variable and it is pointing to my .dgnlib file.
What database is it looking for and where does it go? Is it in the .dgnlib file?
Thanks.
↧
Connect Series w/ OpenRoads Main Tools Functions Missing
We just installed OpenRoads for Connect and I'm missing a few major tools within the Civil/Main tools. The Manipulate tools are now missing the Move Parallel and Move to Contact functions, and the Modify tools are missing Break Element. In their place is a description that says, for example, "Civil Main/Manipulate/Move Parallel", but when selected, nothing happens. The icons are also missing. I've tried opening a list and adding these missing functions but they don't appear and nothing works. I have to search for the function in order to get a dialogue.
Is there some workaround or update that fixes this? I'm running on the most recent version as of 11-20-2019.
↧
ORD - corridor object window doesn't show up in one file, but not problem in others
Corridor object window doesn't show up only in one files. Other files not problem. Is it a problem with the file?
↧