Still struggling to figure out why the CL point isn't available for labeling. Any other ideas?
↧
RE: OpenRoads Annotate Cross Sections
↧
RE: OpenRoads Annotate Cross Sections
Well, I downloaded your dgnlib and had a look.
Because it took me a while to find the feature definitions, for others I'll say that the feature definitions are found under Feature Definitions/Linear/Modeling. (It wasn't entirely obvious, and I hadn't seen anywhere else in the thread that would have told me.)
Selecting all three of the features you mentioned, and cycling through them in the Element Information window, I see that the templates used for plan, profile, 3D, and projected profile are all appropriate for its specific feature definition. Other than this, the only difference that I see in all the feature definitions is only that the EOP feature creates template geometry. Since the EOS feature is properly labeled, this can't be the problem. All of them use the same template for cross sections: Modeling\Points\XS_Label Point Indicator as you noted.
I see that the templates for each of the features in plan, profile, 3D, and projected profile are all identical except the level, and they have only general settings. They're all primary elements. The cross section template has 'x' for active points, so that's good.
However, I see that the Classes setting on your template XS_Label Point Indicator has both construction and primary. I don't know whether that matters. Have you confirmed that your CL points are construction or primary? That may matter.
I see nothing else that could possibly have any impact.
Because it took me a while to find the feature definitions, for others I'll say that the feature definitions are found under Feature Definitions/Linear/Modeling. (It wasn't entirely obvious, and I hadn't seen anywhere else in the thread that would have told me.)
Selecting all three of the features you mentioned, and cycling through them in the Element Information window, I see that the templates used for plan, profile, 3D, and projected profile are all appropriate for its specific feature definition. Other than this, the only difference that I see in all the feature definitions is only that the EOP feature creates template geometry. Since the EOS feature is properly labeled, this can't be the problem. All of them use the same template for cross sections: Modeling\Points\XS_Label Point Indicator as you noted.
I see that the templates for each of the features in plan, profile, 3D, and projected profile are all identical except the level, and they have only general settings. They're all primary elements. The cross section template has 'x' for active points, so that's good.
However, I see that the Classes setting on your template XS_Label Point Indicator has both construction and primary. I don't know whether that matters. Have you confirmed that your CL points are construction or primary? That may matter.
I see nothing else that could possibly have any impact.
↧
↧
OpenRoads Annotate Cross Sections
Good afternoon,
I was wondering how I can find information on how to annotate cross sections. I have created a corridor with PowerGEOPAK OpenRoads SS4 and have created the cross sections from that corridor (two separate files). When I go to annotate the cross sections, I either get no annotation at all, or the little I do get is not the annotation that I wanted. For background information, we are using PowerGEOPAk with a template library and predefined preferences for cross section creation and annotation that we received from a client running InRoads OpenRoads SS4. I haven't been doing this too much with OpenRoads, so I don't know my way around, and the "Help" is less than helpful (blank actually). I am familiar with the GEOPAK Corridor Modeling method of annotation, but I don't see those little text tags when I create the sections. How does the annotation tool know what to label? I see some of my template point names in the "Annotate" area, but I don't see my centerline point.
Anyone have some insight?
Thanks,
Ken
↧
RE: OpenRoads ConceptStation - Profile VPI handles missing
Andrea,
Check if the handles are turned off in the tool settings window.
Pick the element selection (Black Arrow) to see these settings
Tom F.
Check if the handles are turned off in the tool settings window.
Pick the element selection (Black Arrow) to see these settings
Tom F.
↧
how to use special ditch grades in open roads
Making the transition from using criteria to develop cross-section to using openroads SS4. During the design phase I would allow the criteria to define the ditch sections. Those sections would be given to the drainage engineer who would develop special ditch grades to control the flowlines. I would then allow the special ditch grades to control the flowlines. I am having a difficult time finding the best way to do this in openroads. I found a video where the ditch was controlled by an alignment and profile but I want the frontslope to control the horizontal location and the profile to control the vertical. Is there an efficient way to do this in open roads? Thanks for your input. Brian
↧
↧
RE: OpenRoads ConceptStation - Profile VPI handles missing
Thanks, but I'm not sure what you mean by tool settings. When I have the profile selected I can't find anything related to the settings. The thing that's strange is that some of the VPIs are showing up and are workable, while others are missing. Thanks, Andi.
↧
OpenRoads ConceptStation - Profile VPI handles missing
Hello,
I'm using ConceptStation and when I select the profile to edit the curves, some of the VPI handles are missing. The profile shows the curve length and K-value, and I'm able to adjust the length of curve but not the VPI. Has anyone had this issue or know how to solve it?
Thanks.
↧
RE: Cross Sections - Existing ground line is appearing at elev (-2,163,317) but proposed ground is at correct elevation
It was a problem with the reference file, 3d model.
Offset X = 0, Offset Y = 0, Offset Z = (-2147483.6470).
Changed orientation to coincident. No change.
Changed orientation back to coincident world and the Offset Z reset to Zero.
Existing ground line now appears correctly in cross sections.
Jonathon Perrego PE
Senior Project Manager,Transportation
![]()
WHITNEY BAILEY COX & MAGNANI, LLC
One Sterling Place
100 Sterling Parkway Suite 108
Mechanicsburg,PA 17050
MAIN717.691.4708 DIRECT717.691.2526 FAX717.691.4749
Senior Project Manager,Transportation
WHITNEY BAILEY COX & MAGNANI, LLC
One Sterling Place
100 Sterling Parkway Suite 108
Mechanicsburg,PA 17050
MAIN717.691.4708 DIRECT717.691.2526 FAX717.691.4749
↧
RE: .NET exception at Bentley.Civil.Geometry.Model.GeometricSpaceCoordinateConverter.ConvertCoordinates
I got the same error as this last one, at Bentley.Civil.CadSystem.Microstation.?A0xa5f372b8.inqmn_PointFilterFunction(_dPoint3d* ptP, Int32 viewIndex, Int32 eventType).
This time, though, is really strange because I was minding my own business in Microsoft Word when this .NET Framework error was raised. Beyond that, I really have no idea what might have triggered it. I'm not really seeing a pattern from my previous reports on this.
This time, though, is really strange because I was minding my own business in Microsoft Word when this .NET Framework error was raised. Beyond that, I really have no idea what might have triggered it. I'm not really seeing a pattern from my previous reports on this.
↧
↧
.NET exception at Bentley.Civil.Geometry.Model.GeometricSpaceCoordinateConverter.ConvertCoordinates
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: [OR CR] Make Corridor Editing as easy at is was in Roadway Designer (and More...)
I have had no exposure to Roadway Designer, but these ideas sound very promising.
Specifically, though, I'm wondering about that first bullet point. "Hover over points and learn point names" -- in what context? Hover over points where? You can learn point names within the template editor and in the dynamic cross sections and in 3D and in plan as well (as long as the plan elements are created). Unless you're talking about an improvement, or something altogether different. Maybe you're referring to Point elements. I thought you could see the point name in the tooltip, though it'd be nice to be able to visualize the point's name (and search in point names).
Of special interest to me is having better access to point controls and parametric constraints. They should be more obvious. So should horizontal constraints due to attached external reference elements. And using external reference elements to establish vertical constraints would be great too.
Specifically, though, I'm wondering about that first bullet point. "Hover over points and learn point names" -- in what context? Hover over points where? You can learn point names within the template editor and in the dynamic cross sections and in 3D and in plan as well (as long as the plan elements are created). Unless you're talking about an improvement, or something altogether different. Maybe you're referring to Point elements. I thought you could see the point name in the tooltip, though it'd be nice to be able to visualize the point's name (and search in point names).
Of special interest to me is having better access to point controls and parametric constraints. They should be more obvious. So should horizontal constraints due to attached external reference elements. And using external reference elements to establish vertical constraints would be great too.
↧
[OR CR] Make Corridor Editing as easy at is was in Roadway Designer (and More...)
These are from memory, so there may be some minor errors in my recollections. But the basics are pretty good.
In Roadway Designer, we could:
- Hover over points and learn point names
- Right click on points to define point controls
- And if there were little colored squares, the right click also offered you the Edit ... Control menu so you could open the Edit Point Control or Edit Parametric Constraint dialog box
- We could see in Plan, where a point control was in effect (although sometimes this was flawed)
- When in a dialog box with lists of controls, we could temporarily sort them by start or stop stations as well as point names or any other columns. In OpenRoads, clicking on column headers does not seem to do anything
- In the Element Template you can reorder children of a group. It would be nice if we could do a similar thing in the Project Explorer tabs. This would allow reordering of point controls and other things on a more permanent basis.
Of these, the inability to sort is pretty big, but being able to select a point control or parametric constraint in the section made working with them way easier than Open Roads.
↧
[OR] Bug: Strange snap behavior in profile
Using Geopak SS4 .878.
Given: an existing terrain model, set as active terrain. (This will work with a jagged profile like one derived from a surface--probably any complex profile. It is not triggered if your profile is a simple parabola.)
- Construct a horizontal civil element. For demonstration purposes, make it something like 300 units long or longer and ensure that it isn't running too far out of the terrain model, if at all.
- Open this civil element's profile model.
- Profile Offset Transition. Use the active terrain surface. Use any offset value (I'm using +3). Have it begin at station 200 and have it run for 100 units.
- Profile Line Between Points. Snap to each end of the offset created in step 3. Intuitively, you know that selecting this element should reveal that it begins at 200 and ends at 300 with a length of 100.
- Select the offset element created in step 3, and move the begin point some distance toward the beginning of the alignment. It doesn't matter so much exactly where, but it needs to be far enough that it will have reached a break line in the terrain model. In my case, moving it 25 feet was enough.
- Now select the straight line created in step 4. Observe that this straight line is no longer following the begin point on the offset element. The begin station will match the station where you'll find a break line in the terrain model. In my case, 199.2157. The end station shifted with the offset element's end station.
- Now if I repeat step 5 again and move it another 25 feet, I see that the straight line element continues to begin at 199.2157. The end station shifts with the offset element's end station.
- Now if I repeat step 5 except now move it 50 feet forward instead of back, I see that the straight line element's begin point moves to another break point in the active terrain model. This time, it is at 296.5232. The end station shifts with the offset element's end station, now back at 300. That means the element is only 3.4768 feet long (longitudinally).
- If I inch the offset element forward to 301 then 302, etc., the end of the offset advances as well, and with it the end of the straight line advances. When the end of the offset element gets past the next break line, the beginning of the straight line hits that next break line as well.
This is where I lose the trail. I'm not even sure sure what it's picking up at this point. This behavior is very confusing.
So now, from what I can tell, I can't trust profile snaps.
↧
↧
RE: IR_SS2 How do I get a template to run when I don't have (don't need) a proposed profile?
I'm using Geopak, so this may not apply to you directly, but it sounds like you need a template (probably using the CL as the corridor's baseline) to do some of the following:
1. Find the lateral position of the ES. (You can do this by specifying the offset in the template or by attaching the ES line as a reference.)
2. Find the vertical position of the ES at the appropriate offset.
The second is apparently what you're having trouble with. Someone else could help better if you explain exactly how you're using it and what response you're getting in the model.
As for what profile to use on the corridor model for the template drop, you should be able to use any profile attached to the CL. Any profile that exists over the range you're interested in, anyway. And for that matter, you could specify the existing profile.
1. Find the lateral position of the ES. (You can do this by specifying the offset in the template or by attaching the ES line as a reference.)
2. Find the vertical position of the ES at the appropriate offset.
The second is apparently what you're having trouble with. Someone else could help better if you explain exactly how you're using it and what response you're getting in the model.
As for what profile to use on the corridor model for the template drop, you should be able to use any profile attached to the CL. Any profile that exists over the range you're interested in, anyway. And for that matter, you could specify the existing profile.
↧
IR_SS2 How do I get a template to run when I don't have (don't need) a proposed profile?
Small Project, Small Budget, not a lot of room for R & D.
I am trying to come up with a template that can run along my alignment, locate the existing shoulder line (plan and elevation) and draw in my new, improved shoulder. There may be widening, but I'll cross that road when I come to it.
How on earth do I make this happen? Can I make this happen?
I can think of how to do it with criteria files, but templates are (to my brain) a very different sort of logic.
Start at center point at existing ground profile
Draw Skip to Plan Element
Draw Skip to existing ground surface
Start drawing.
I don't see any way to tell any point "start on existing ground". I see Project to Surface, but I must be using it wrong.
I'm at the crossroads of fighting to get a template (any template) to work and just drawing the darn sections by hand. That's not very helpful and it won't teach me a thing, but time and budgets don't always allow for time to figure out the "best" way to do anything.
MaryB
↧
RE: Draped Aerial Imagery and Display
What display style are you using? Wireframe? Smooth? Illustration? Try using a different one and see if that does it. Also try clicking the magnifying glass next to where you select the display style to see more options available to different render modes.
If not, try toggling fill on and off if you haven't already.
If not, try toggling fill on and off if you haven't already.
↧
Draped Aerial Imagery and Display
I was able to successfully utilize the video above to drape the aerial image onto the terrain. Since the aerial is assigned to the triangles, i cannot turn one off without turning off the other. Therefore, i cannot display the aerial imagery on the 3D model without the triangles overwhelming the screen. Is there a way to turn off the triangles while still displaying the aerial imagery?
Thanks,
Chris
↧
↧
RE: [OR CR] Make Corridor Editing as easy at is was in Roadway Designer (and More...)
That wasn't me that wrote that. That was Chuck. But I would guess the same--that he was referring to the corridor objects dialog.
But unless you are looking at Civil Accudraw, the "station" you get when snapping in a profile model is simply the distance from the beginning of the chain. The Civil Accudraw window does report the station correctly according to the alignment's stationing; from my experience, the coordinates in the status bar do not.
But unless you are looking at Civil Accudraw, the "station" you get when snapping in a profile model is simply the distance from the beginning of the chain. The Civil Accudraw window does report the station correctly according to the alignment's stationing; from my experience, the coordinates in the status bar do not.
↧
RE: [OR CR] Make Corridor Editing as easy at is was in Roadway Designer (and More...)
That would be nice if the status bar coordinates could be made "Civil" aware and report Station Elevation using that format when in a profile view and Offset Elevation using whatever format is defined in Civil Preferences +/-, LT/RT, Elev=, etc
↧
RE: [OR CR] Make Corridor Editing as easy at is was in Roadway Designer (and More...)
Right Click menu. Go figure...
Thanks!
The Hover Over on points was available even though the section view did not really display any points, except for Null Points, if display was enabled. In the Open Roads cross section view, many of the settings are not clearly defined. I sometimes get crossing point displays and sometimes I don't. And when I do, sometimes their size seems completely arbitrary. But knowing what each colored square on a point means - I believe it might be described in the old Roadway Designer help, but I could not find them explained anywhere on the communities nor in the help.
Being able to right click on them to open the control dialog box driving them was a real time-saver (and head scratch avoider) especially when revisiting a model that you created weeks ago. And having them highlight in plan and profile while selected in the control dialog box also helped you recall or figure out the possible reason for a control.
A few years back, I had to jump into a number of very complex Roadway Designer files created by others, on a project I had no familiarity with, other than knowing the city and its street pretty well. Without these capabilities, I do not believe I would have been able to get up to speed as quickly as I was.
↧