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

RE: .NET exception at Bentley.Civil.Geometry.Model.GeometricSpaceCoordinateConverter.ConvertCoordinates

August 9, 2016, 1:42 pm
$
0
0
I got an identical error in an entirely different workflow. (The entire stack is surprisingly identical, including Bentley.Civil.CadSystem.Microstation.?A0xec45a7bb.inqmn_PointFilterFunction.) This time I was manually setting up a superelevation point control (not using the usual superelevation application button).

The first prompt for a point is simply "Locate Point", not "Locate Pivot Point" or "Locate Reference Point" some such. So I selected the wrong edge of pavement. Then when the other prompt came up, I selected the same point and I just figured I'd fix it later. It never got there, as this exception came up.

Other than the identical stack, though, how I got these exceptions was an entirely different process.
↧
Search

.NET exception at Bentley.Civil.Geometry.Model.GeometricSpaceCoordinateConverter.ConvertCoordinates

August 5, 2016, 1:37 pm
$
0
0

This exception was raised when I attempted to use the dynamic cross section view to establish the beginning station for a variable offset profile line.

System.NullReferenceException: Object reference not set to an instance of an object.
   at Bentley.Civil.Geometry.Model.GeometricSpaceCoordinateConverter.ConvertCoordinates(SmartPoint smartPoint, GeometricSpace targetSpace)
   at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.ConvertSmartPointToViewCoordinates(SmartPoint smartPoint, IViewport viewport)
   at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.DoFixPoint(IEditableButtonEvent cursorEvent)
   at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.OnFixPoint(IEditableButtonEvent cursorEvent)
   at Bentley.Civil.CadSystem.Microstation.MstnInputManager.OnPointFilterEvent(_dPoint3d* ptP, Int32 viewIndex, Int32 eventType)
   at Bentley.Civil.CadSystem.Microstation.?A0xec45a7bb.inqmn_PointFilterFunction(_dPoint3d* ptP, Int32 viewIndex, Int32 eventType)
   at Bentley.Internal.MicroStation.CoreHook.DispatchNoHandler(UInt32* argStack, UInt32 mysp, IntPtr pFunc)
   at Bentley.Internal.MicroStation.CoreHook.Dispatch(UInt32* argStack, UInt32 mysp, IntPtr pFunc)

I clicked the button to activate the tool, then I clicked the profile from which I wanted a variable offset. When asking where it should start and what the offset should be, I simply moved my cursor into the dynamic cross section window and it immediately froze.

Using Geopak SS4 .872.

It is not reproducible, that I can tell. I tried the operation again and it seems to work fine.

↧
↧

RE: [OpenRoads] Synchronising Feature Definitions

August 9, 2016, 1:44 pm
$
0
0
Have you tried right-clicking the Feature Definitions entry, though, to see what commands are available? I wouldn't know what else to do to synch them other than simply delete all the (appropriate) entries within your working file, in hopes that the attached dgnlibs will take over at that point.
↧

RE: [OpenRoads] Synchronising Feature Definitions

August 9, 2016, 1:54 pm
$
0
0
Yes, I looked at the available options..

Deleting crossed my mind and I tried it as well. The problem is when I delete feature definitions from the active model, it also deletes feature definition assignments from elements! I'm working with suda model is this makes any difference.
↧

[OR] [CR] [Bug] Superelevation constraints

August 9, 2016, 4:28 pm
$
0
0

By default, these key points have no slope constraints or distance constraints. I am trying to gather experience in how to effectively use them manually. Any additional observations on this would be welcome indeed. I'm sharing mine here.

Distance Constraint

This locks the longitudinal positioning of the key point according to another specified key point.

Bug: The value of Offset seems to be taken as meters instead of working units, in Geopak SS4 .872.

Cross Slope

This locks the slope to the same slope at the already-established key point provided.

Mirror Cross Slope

This locks the slope to the negative of the slope at the already-established key point provided.

Vector Slope

When using the slope constraint Vector Slope with Slope Transition 1 set to the first key point and Slope Transition 2 set to the second key point, what I'm seeing is that it does nothing but allow you to see what the cross slope should be at any given point along the superelevation element. I mean, wherever I place my intermediate key point, the cross slope seems to be simply an interpolation between the two key points. Not too useful, that I can tell. It's conceivable that it might be useful when working with more than one superelevation lane.

Wish list

I'd like to see the option to lock in a rate of change (ROC) coming from a back key point and another rate of change coming from an ahead key point. For example, an ROC of 0% per foot from one and an ROC of 0.06% per foot from another. With those inputs, it would establish an appropriate longitudinal position for the keypoint.

↧
↧

RE: [OpenRoads] Synchronising Feature Definitions

August 9, 2016, 4:32 pm
$
0
0
Thanks for sharing that observation. If you ever find the solution, I'd love to hear about it.

Inconsistently, I sometimes see that my linework that follows a feature definition isn't rendered with the proper element template and I'm not sure whether it's an Element Template issue or a Feature Definition issue. I guess it's kind of a simple matter to whittle that down, but I don't recall in what files I've seen this behavior. It might be the same problem as you're having.
↧

RE: InRoads SS2 - Edit Vertical Geometry opens Create Surface Dialog

August 9, 2016, 10:25 pm
$
0
0

Tom, there are two things that activate this type of behavior. One toggle is in the Application Add-ins, and one is in the Variable Manager. You would want those options off if you are not using this functionality. (Actually you have to have both of those toggled on to initiate that, so by toggling either one off it will stop, but I would just turn both off if you aren't using it.) If you want to know more about this capability let me know, but I assume that you really mostly find it bothersome and would like to disable it.

↧

InRoads SS2 - Edit Vertical Geometry opens Create Surface Dialog

August 9, 2016, 6:55 am
$
0
0

Hello,

InRoads SS2 8.11.07.536. After making an edit to vertical alignment, the create surface dialog opens.
What setting would cause this?

Thanks,

Tom F.

↧
Search

RE: [OR] [CR] Templates: unexpected recursive constraint with Vector-Offset

August 9, 2016, 11:29 pm
$
0
0
Derek, in my opinion I wouldn't say this is an error. Theoretically-speaking, If the EP has the Parent of both Constraints tied to the ETW (in essence making the location of the EP controlled by the position of the ETW), then it would seem correct that you can't then tie the slope of the ETW to the relative position of the EP (or vice versa) That creates two moving targets. That's the recursive piece. Why don't you create a NULL Point and tie it to the ETW's and then define your EP from the NULL Point? That way the constraints aren't cross-talking. ... I'll qualify this post with the fact that I'm saying this while using InRoads SS2, not OpenRoads SS4.
↧
↧

[OR] [CR] Templates: unexpected recursive constraint with Vector-Offset

August 9, 2016, 10:01 am
$
0
0

I was given a template that is intended to place 2 lanes of pavement on the left carriageway. I found that it didn't serve my purposes as well as I liked. It places 14' of pavement to each side of the baseline: 12 feet of lane plus 2 feet of shoulder with full depth pavement. I want to add a point that represents the edge of travel way (ETW) and then set the pavement edge (EP) 2 feet outside that.

The above establishes that superelevation is pinned to the EP in the template that was provided. I haven't changed it.

I'm adding points called ETW-L and ETW-R. I constrained each to be offset from the centerline, with an appropriate label for parametric constraints. I constrained each to Vector-Offset (0') between the centerline and the edge of pavement (which, as noted, is how superelevation is set). 

The EP points as provided were constrained horizontally from the CL (14') and by slope from CL (2%). In the process, I re-set the horizontal constraint (the first constraint) on the EP points: Setting it to be derived from the near ETW then pressing Apply, I get the message: "ERROR: The first constraint could not be placed because: Invalid Parent - Causes recursive constraints".

The workaround is that on the ETW, I need to change from Vector-Offset to Slope, and use the same CL and EP points to establish the slope. At that point on the EP I don't get the recursive constraint message when I set the horizontal constraint to the ETW. This workaround isn't a great deal of work, but surprising, as it is not obvious. And if this recursion had been deep enough, it might not be obvious where it started.

In the end, I suppose I'm asking that this error be fixed or explained.

↧

RE: [OpenRoads] Synchronising Feature Definitions

August 10, 2016, 12:04 am
$
0
0
My problem is slightly different however, from time to time I also experience a behaviour you mentioned. We built our utility models using FDs without trench template assigned to them. Now, we are in need to apply trench template so I updated FDs in dgnlib but don't know how to force my local copies of FD to synchronise with dgnlib. I mean I know how to do this manually but I would expect it can be automated similarly to levels or element templates.

Can someone from Bentley log an enhancement request if there is no such facility at the moment please?
↧

[OpenRoads] Synchronising Feature Definitions

August 9, 2016, 10:06 am
$
0
0

Hi,

is there a method for synchronising local copies of Feature Definitions with those in dgnlib? There are "Update from Library" for Element Templates and Levels, is there similar tool for Feature Definitions?

Thanks,
Krzysztof

↧

RE: Place cell/Block Tool in PowerCivil

August 10, 2016, 4:24 am
$
0
0
Hi Chris,

Thanks for the quick respond. It makes sense as I used to use Bentley Rail Track and have switched to PowerCivil recently and couldn't find the Tool.. Do you know if there is another way/work around to annotate crossections with cell/block in Inroads??
↧
↧

RE: Place cell/Block Tool in PowerCivil

August 10, 2016, 5:48 am
$
0
0

You can place cells in a cross section when displaying breakline features as 'crossing features' in a section.  You would need to have these surface breakline features generated and it can display a cell or symbol at the locations where the feature(s) cross the sections.    

Another option is to just use the place cell command in MicroStation (CAD platform portion of PowerCivil) but it would not have any civil intelligence and would not be tied to the cross section set, merely a graphic created but it can be rotated and scaled just using the MicroStation/CAD tools.

↧

RE: [OR] [CR] Templates: unexpected recursive constraint with Vector-Offset

August 10, 2016, 6:39 am
$
0
0
I disagree that this isn't a bug. Or, perhaps it's better to say it is surprising to see this error raised. If it isn't a bug, it might be helpful to know why it behaves this way for vector-offset and another way for slope.

Using the vector-offset constraint on the ETW and setting the parents to CL and EP raises the recursive constraint error.

Using the slope constraint on the ETW and setting the parent to CL and locking the slope to follow the slope between CL and EP does not raise the recursive constraint error.

I'd always considered vector-offset (when the offset given is 0) to be shorthand for using the slope constraint, so to me they should yield identical performance and identical errors. If you can explain to me how my understanding is fundamentally flawed, I'm all ears.
↧
Search

How can I calculate the quantities of groundwork from lots of different terrains?

August 10, 2016, 6:58 am
$
0
0

Hi, 

I've got to determine the quantities of groundwork from dozens of different terrains. The quantities must have the following properties:
-The floor of the terrains are flat and must be calculated to the existing ground level;
-I need quantities per terrain (see image).

Now the most efficient way I can imagine is to create polygons and use the Vertical Geometry Tools to get the elements at the correct Z. 

-Sidestep: Now the client want to change the Z of the elements. I have to Open the Profile view and change the heights or set the new height active. This only can be done one by one. I've got dozens of elements (??).

create a terrain per field one by one (lot of work, see image above). After that I use the Create Cut and Fill Volumes Tool and use this also by al the fields one by one (also a lot of work). After that I have to calculate the quantities. In PowerCivil I can use the Analyze Volume Terrain model. But also here I have to do this one by one (??). 

Fortunately I can use Labels in MicroStation Connect Edition in combination with the created meshes (from the create Cut and Fill Volumes Tool) for this task, but despite that it's all is very cumbersome.

Does anyone know a more efficient workflow for this?

A desired workflow (Tip for Bentley):

-Select all hundreds of elements and use a create terrain by shape boundary. Hundreds of different terrains are created with the shape as boundary;
-If the client want a different Z, select all elements and use a Profile by constant elevation and set active tool;
-Select all terrains and use the Create Cut and Fill Tool from Volume tool;
-Sidestep: A tool where the volumes are splittet by ground layer (a Certain depth from ground level or constant elevation);
-A function where all quantities are automatically placed as a text in the center of the volumes.

↧

RE: [OR] [CR] [Bug] Superelevation constraints

August 10, 2016, 7:25 am
↧
↧

RE: Show geometry coordinate tabular

August 10, 2016, 7:29 am
$
0
0
Using the InRoads explorer > Geometry > Vertical Curve Set > Table Editor which will allow you to edit the vertical alignment.
↧

RE: InRoads SS2 - Edit Vertical Geometry opens Create Surface Dialog

August 10, 2016, 7:38 am
$
0
0
Mark, Thanks so much, we'll give that a try Tom F
↧

RE: Show geometry coordinate tabular

August 10, 2016, 9:45 am
$
0
0

Coming from the Civil 3D side, if you were around during the Land Desktop Years, InRoads (along with GEOPAK and MX) are all Civil/Site platforms that are the precursors of Open Roads.

Unlike Autodesk, Bentley decided to implement a gradual migration from its 3 "native" programs to a unified platform called Open Roads. As they updated those three platforms, they added tools and capabilities. In most instances, these additions were actually migrated from one of the three platforms to the other two. For example, the template  editor and corridor tools originated in InRoads as its Roadway Designer. The tools that are part of Civil Cells probably have their origins in the MX Roundabout tool. And the general site modeling originated with the GEOPAK Site Modeler. The Civil Geometry tools also seem to resemble many of the GEOPAK Civil geometry tools.

This version is still a hybrid of native platform - in your case (Power) InRoads and Open Roads. When you use the tools within the non-InRoads task menus, you are using Open Roads. If you use the InRoads Explorer or InRoads Task tools, you are using InRoads. And certain workflows actually create native geometry files while using Open Roads tools.

To create the profile view used for plan sheet preparation are only available in the native platforms. Cross Sections or integrated into the Open Roads tools.

↧
Viewing all 15087 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>