Quantcast
Channel: OpenRoads | OpenSite Forum - Recent Threads
Viewing all 15087 articles
Browse latest View live

RE: Importing Autocad file

$
0
0
1. The latest version of MX is 8.11.9.878 - what is the number you posted '6.1.7601.17514'?

2. Does the coordinate data in the ACAD file match the coordinate data in the CSV file? That would be the first thing I would look at. Did the ACAD file get referenced interactively (rather than coincident), which would put it in the wrong position.

Importing Autocad file

$
0
0

Dear Sir 

          Am facing problems while importing autocad file (Some of the file are not import as DXF file). Is there any another method to import autocad file with levels (without take it as reference file). Presently the way am following is File---->Import---->ASCII file, but it is not working for more data files(AutoCad files).

RE: SS4/ Openroads orphaned components in 3D view can't be deleted

$
0
0
I have the similar problem with the latest SS4 PowerInroads release (.878). corridor is procesing and it displays component that does not exist in my template. It was in one of previous template versions. I am changing templates and even with a different "dummy" template, this strange component is displayed in 3D view. any idea how to get rid of this component?

RE: SS4/ Openroads orphaned components in 3D view can't be deleted

$
0
0
Adam, Chris Key was able to clean up my file for me after I sent ti to him. I believe he has tools not available in the standard SS4. This is a serious issue, that I've been hoping Bentley would fix. However they've moved on to their new software now, so I'm not going to hold my breath. Good Luck:)

SS4/ Openroads orphaned components in 3D view can't be deleted

$
0
0

 I'm working with SS4/openroads. There are old components showing up in all of my views. They are not associated with my corridor and I cannot delete them. How can I get rid of them? And what may have caused this in the first place? See screen shot above:

RE: Major bug in PowerCivil an PowerRailtrack

$
0
0
I downloaded your file and ran a quick test, creating a corridor and dropping a template. All I have supplied in the file is a complex geometry so it couldn't be a complete test because it couldn't solve end conditions against a terrain (no terrain in the file), but it processed a backbone template fairly quickly (took about 1 minute to create the corridor and process the corridor).

In order to fully test this issue, we will need a good dataset you are using with terrain model and templates. We will need a description of how you are creating the corridor with template names and stations you are using, etc.

You may can try creating a straight tangent geometry and create the corridor just as a test to see if it could be something with the original geometry or the complexity of that alignment.

Are you using the same workspace in the different versions you are testing?

If we can get the full data and reproduce the issue, we can then troubleshoot to find a possible issue or log a defect if warranted.

RE: Inroad additional lane work issue

$
0
0
Hello,

V8i SELECTseries 3 (08.11.09.459) is the version of MicroStation you have installed. What version of InRoads do you have installed? This will determine which tools you will use and in turn, allow me to better assist you.

Thanks,
Sanders

Inroad additional lane work issue

$
0
0

Hi everyone, I am new to Microstation and Inroads area. Using V8i SS3 8.11.09.459. I am still on the job training and got a new project where two lane two way road will need to add a bus lane turning left on one side. I need to make design surface and cross sections. make the dedicated left turn added to the existing design. Can some one give me idea about which tool to use? Do I need roadway modeller or template kind of thing? or design normally in Microstation with normal cross sections? If need to use template how the transition between old template and new template will work? Help please. 


RE: [OR] Failure to project entire feature's profile to other element

$
0
0
What happens if you take the projection in segments and use the "Project Profile Range to Element"? For example, use the projection up to the gap where the bridge is located and do only that segment? Does it include all of that specified range or is it still stopping at the same location near the beginning as it does when you Project Profile to Element?

One thing that does also throw a flag is your mention of the series of arcs that create a 180+ degree turn so the alignment loops back on itself. You may also try to run the projection range to a point in the curve, splitting the projection. Then once you have all the projected profiles, create the profile by complexing the elements.

This is certainly not ideal if you were able to perform this is other cases, but I would like to see if it creates the projection differently.

Trimming 3D Mesh Without adding extra vertices

$
0
0

Hi, 

I am creating a 3D model for a proposed Highway and I need to trim the limits of the mesh for breaks in the road at bridges. I have found a couple different ways to trim the mash to match the correct limits, however, each method creates a bunch of extra vertices. The top surface i still drawn in correctly which is good, however for turning in final plans I would like to have a more aesthetically pleasing model. 

Below is a summary of each method I have used to clip the mesh. There appears to be no rhyme or reason to why the extra vertices pop in, because one side will do it and another will not and it varies, sometimes it will add them and other times it will not.

Please let me know if anyone first of all knows why it is doing this, how to trim the mesh object without adding the extra vertices and if someone has a better or more efficient way of trimming the mesh objects I am open to suggestions.

Thanks, 

Layton

The first method I used to trim the model is using a fence clip to trim the mesh back to the limits. The pictures below show the begining and end result of the trimming. As you can see in the second picture there are extra vertices drawn in the components fence. 

The other method I tried using was the "Mesh Project" Tool: 

I had similar results using this tool as shown by the pictures below. 

[OR] Feature Definition Properties - Detailed Explanations for Settings Not Coming From Native Products Needed

$
0
0

On my current assignment, we have been thrown into the deep end of the pool and told to swim.

Additionally, I am on a committee looking to assist our local DOT to migrate to Open Roads From InRoads Ss2 (and earlier.)

For the current assignment, they seem to have thrown together a composite workspace coming from Bentley Civil Imperial and other DOT's. Unfortunately, the agency that this project is ultimately for, does not provide anything other than a pure MicroStation workspace with no element templates. So much of the Open Roads design work is creating elements on non-standard levels or in a worst case scenario, having the workspace force elements to Default is displayed in a compliant workspace environment (level creation disabled).

So I am frequently trying to adjust settings as I work to get a desirable result.

This thrusts me into the subject area - needing an in-depth explanation of many of the settings in the Feature Definition Properties. As a CADD Manager, I want to keep as many items in an XIN file as possible - only extending settings into DGNLIBS that cannot be accomplished from an XIN alone. So I want to use Native Style wherever possible. This allows me to edit my workspace settings using only my trusty text editor - Notepad++.

But in many areas, the help file does not fully explain many of the Feature Settings now in DGNLIB's and also many of the Element Template settings that are extensions from pure MicroStation.

Here is a small example:  In the Help file, under the Terrain Modeling Toolset > Terrain Model Analysis > Feature Definition > Notes for InRoads Users is this bullet:

  • Linear Feature Definitions - You must toggle on one of two linear settings, the Feature Style, Surface Feature > 3-D Plan Surface Display Line Segments or General Line Arc Spiral.

I do not see any location for this in any dialog box. But I do see in the Feature Properties dialog box, a Linear Default Settings that has only mentions in the help file, under the first Feature Definitions topic: 

In addition, the behavior of a feature when used is defined in a features definition. This includes if a feature is automatically annotated, naming of the feature, exporting the feature object to the native product, creation of corresponding 3D elements and the option to link a corridor modeling template to the feature. 

We need a much more detailed explanation of what these things do, what they effect, etc.

Even the Best Practiced manual does not go into sufficient detail on these topics

Bentley i-model ODBC driver Error message

$
0
0

Dear Collegues, I need help in resolving this problem on my laptop. During installation of all the main Bentley software (Power InRoads ss4, Microstation V8i ss4, AECOSIM) I encounted a similar screen and error message.

If it is linked to Microsoft softwares then I have no idea why this is the situation because I have all the relevant licenses. I sought help from Microsoft silver partner (paid service) yet this problem persist.

What  problems would i encounterI should expect if this persist.

I downloaded and installed these drivers from Bentley website but it hasn't helped.

I will appreciate any assistance I can get. Thank you in advance.

RE: [OR] Failure to project entire feature's profile to other element

$
0
0

I have a new odd observation, possibly related, possibly unrelated to this problem. When I use Project Profile To Element to project from LOW-R to P-DCH-R, the lines in the plan view showing the projection don't show up unless all of P-DCH-R is in the viewport. When I use the same tool to project from LOW-R to another plan element, it doesn't matter that I'm zoomed in to one area of the other element.

On the other hand, when I use the same tool to project from the construction limits line to P-DCH-R, the lines in the plan view showing the projection do show up. The lines showing the projection show up, but when I commit to the projection, the same thing happens as happens when I project LOW-R to P-DCH-R. Namely, that the projection runs only from about Sta. 5+00 to Sta. 15+00. (I realize that not all dynamic cross sections have all the same points and therefore the entire length may not have continuous linework. I did confirm that the projection of the construction stakes should have run up to the end of P-DCH-R.)

When I do see the lines showing the projection in the plan view, the entire north end of the alignment--the part where the loop is--is crazy.

(Ignore the labels; they aren't relevant to this issue.)

Apparently the tool decides on a couple points that a bunch of the projection should converge on, and between these two points there are normal projections. (The point of convergence near the end of the alignment appears to be coincident with the end of the template drop.) Meanwhile, one of those key points and much of the normal projection is on an extension of P-DCH-R. Even so, the projection onto the profile runs only to Sta. 15+00, as mentioned above.

When I use Project Profile Range To Element from LOW-R to P-DCH-R, whether I lock to the beginning and end of the alignment, or I use a very small (non-looping) subset of the alignment, I get the same results as you can expect with the knowledge that nothing will show up after Sta. 15+00. 

When I use the same tool from the construction limits to P-DCH-R and lock to beginning and end of the alignment, I get the usual projection up to Sta. 15+00, but also a flat horizontal line from Sta. 34+31 to the end, Sta. 48+30. (Sta. 34+31 seems to be the point on P-DCH-R's loop that could be considered to be diametrically opposite to Sta. 48+30.) When I use the same tool for the same elements but limit it to any segment to the north, unless that range spans both Sta. 34+31 and Sta. 48+30 nothing shows up. When that range does span both points, I get a flat horizontal line with just those 2 key points as VPIs.

With this new knowledge, I decided to look into projecting LOW-R again. 

I projected LOW-R to P-DCH-R from Sta. 32+00 to Sta. 38+00: nothing. From Sta. 32+00 to Sta. 46+00: nothing. From Sta. 32+00 to Sta. 47+00: a decent-looking profile which runs from Sta. 34+08 to Sta. 46+31. From a look at the cross sections, this profile seems to match the model. (That was to confirm that it wasn't longitudinally translated.)

At this point, I have no idea what's going on or why.

I was hoping it wouldn't come to this, but I could do a secure upload of the file.

[OR] Failure to project entire feature's profile to other element

$
0
0

I've done this scores of times, so I'm not sure why it isn't working for me today, in this particular situation. I'm running Power Geopak SS4 .878. It affects my coworker who is using .872.

For establishing proposed special ditch grades to the right, my workflow is that I establish a P-DCH-R that is collinear with the alignment on which the template is dropped. Then I project the typical ditch profile LOW-R onto this P-DCH-R line. From there, I establish whatever special ditch grades I require.

Normally, it works fine, with no issues. (This is the first time I've seen that didn't behave as expected.) In this case, the corridor does have a bridge, so there's no ditch line over that range, but the rest of it does have LOW-R which should project on P-DCH-R just fine. Of course I'm expecting a gap where the bridge is, but I'm expecting the projection to have points everywhere else.

This time, this workflow doesn't work. What I'm seeing instead is that there is a small segment of the projection from LOW-R somewhat near the beginning of the alignment. After that, there is no more projection.

With a slight adjustment--offsetting P-DCH-R from the alignment by, say, 65 feet to the right, it works fine, and from a quick glance it looks like the projection is complete where I expect it to be. Further adjusting the offset and keeping an eye on the profile, at an offset of 58' or lower, the projection doesn't show up properly. At an offset between 59' and 250' it does show up properly. At an offset of 260' or more, the projection doesn't show up properly again, but this time it does show information that isn't shown at 58' or less.

It might be worth noting that this alignment does involve a series of arcs that ultimately constitute a 270-or-so degree turn, but the largest delta for any single arc is 116 degrees. The minimum radius for this series of arcs is 350'.

It might be worth noting that the typical ditch toe is offset 34' to the right of the baseline, compared with the 59' offset required for the entire length of the projection to behave.

Any thoughts on how this is behaving this way?

RE: [OR] Corridor Throws Error When Attempting to Edit a Parametric Constraint

$
0
0

Why can't you use the Corridor Objects tool? Does it work for none of your corridors, or just that one?

Have you tried turning it off and back on? using the key-in "civil display browser"? That might fix the problem of the Corridor Objects tool, and it might solve your most immediate problem too.

Or, as my mom says, it might cure what ails you and might help besides.


[OR] Corridor Throws Error When Attempting to Edit a Parametric Constraint

$
0
0

I cannot open the Corridor Objects tool (Bucket Icon) so to modify a corridor I have to use the Properties dialog box selected from the Project Explorer.

I was trying to change the stations for a Parametric Constraint but when I would edit the station I would get a Property is not Valid dialog box with Details of Object reference not set to an instance of an object.

Next I tried to simply change it from Enabled = True to False and the same thing happens and eventually the MicroStation has stopped Working dialog box opens.

How can I recover a working and editable corridor from this file?

RE: [OR] Corridor Throws Error When Attempting to Edit a Parametric Constraint

$
0
0
What the begeezus is that?

On my (and others) PC's it seems like our corridors get this way very quickly.

Keyed in "civil display browser" and played with a few buttons. Got a nice display of Green "objects".

After that, tried the Bucket tool - Bam! Try to ID my corridor and get the Bentley "email us the error" dialog box, followed by the Abort, Ignore, Retry dialog box.

Try again and get an Dot Net Exception and shortly thereafter, the software crashes and closes without any warning.

RE: [OR] Survey foot-International foot scaling observed in complex terrain model where all models are in survey feet

$
0
0

When you say "Survey DTM", is this a native surface that is stored in a DTM file? Or is it a terrain model? If it is a native DTM, you will need to convert the data using Surface>Edit Surface>Transform Surface.

RE: SS4 Superelevation disable interpolation

$
0
0

Interpolation isn't the right term here: rounding is. I just realized that interpolation works when interpreting it as interpolation between, say, 0.060 and 0.062 to get 0.061.

Anyway, it's probably in your workspace settings.

When you go through the process of computing your superelevation after you've created your lanes, do you specify a preference file? My workspace has one, and it seems to work fine.

My settings are in a .sep file which specifies an eTableName file ( .csv format). Oddly enough, eRoundingIncrement is 0.1 but the results I get are rounded to 0.2%.

Anyway, have a look at the value of CIVIL_SUPERELEVATION_RULES_DIRECTORY and look for .sep files.

SS4 Superelevation disable interpolation

$
0
0

I'm using AASHTO 2011 standards, which state that superelevation rates should be rounded up to the nearest 0.2%.  When I run through the superelevation template creation, I'm getting a value of 5.9% instead of 6.0%.  Is there a flag I need to set to disable interpolation and/or one to have it round up to the nearest 0.2%?

If not, I guess i'll have to do it manually...  womp womp.

Viewing all 15087 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>