I deleted a chain by accident. Used the undo command to bring it back the graphic element. The chan no longer displays in Cogo. Is there a way to quickly recover this or do I need to recreate it somehow? Don't really want to lose my PGL, corridor, ....
PowerGeopak SS4
When a SUDA node feature definition is configured such that the top cell and bottom cell combine to form a minimum depth of less than 1 meter, placing the node results in a 1 meter depth.
A good example is in the bentley sample library. The cells for feature definition sanitary sewer cleanout should result in a minimum depth of 1.89 feet (.57 m). But when placed, the depth is assigned as 3.28 ft (1 meter). This occurs for any node whose 3D cells combine to a minimum depth of less than 3.28 ft (1 meter)
The help files are not displaying in Microstation/PowerGeopak v08.11.09.872 on Win 10 OS. suggestions?
In Ss2 and Earlier, if we were tasked with looking at alternate designs, we could copy a corridor with a new name and then modify the copy. Also, on occasion it has been necessary to split a corridor into two so that target alignments/features that loop do not result in multiple solutions. Again, that was accomplished by copying the corridor and changing the start and stop stations so one ended where the other began.
So how can one accomplish this in Ss4? Is it only possible using a Save As to another file? If so, we may need a CR to provide tools for copying or migrating civil objects within files or to other files.
Anyone know why the tool tips boxes in InRoads are blank or flashing text? Windows 10. Power InRoads SS2. 
When we cut cross sections, our existing ground is missing. The dynamic views clearly shows it - and it is coming from a Reference Model.
Our corridor had no problem targeting it in this manner.
Also, when we get to the General leaf of the Create Cross Section tool, not all 8 views can be selected to make the drawing models - and as mentioned in the subject line, the Help is still refering to Ss2 and Earlier workflows (Surface Properties - Advanced to control surface display). - Follow-up: This is what the help tells you if you open it from the dialog box.
In the Help from the Task menu, it makes the following seemingly contradictory statements:
A cross section is a two-dimensional window of graphics representing a planar section of a three-dimensional (3-D) model. Typically, the 3-D objects displayed in cross section are terrain models and objects such as the existing terrain or a proposed road. The graphics showing a terrain model in a cross section is a cross section surface.
Two paragraphs later, it states this:
When you create one or more cross sections, you choose which surfaces to display. Each cross section displays the selected surfaces as they pass through the window. Each surface is represented in the cross section by a data line known as a cross section surface.
This wording seems to indicate there is still some sort of Surface Selection process as opposed to a section simply cutting whatever is seen in a certain view.
Our Dynamic Section view is 5 but the view list in the dialog box is missing 5. And once the section is cut, there seems to be no way to add other graphics into a set.
What are we missing here?
Why do I get this message in part of my profiles "Element is in a model not allowed by this tool"?
When I try to use GeoCoordination to import a terrain for Concept Station I get the following error:
The downloaded terrain files contains no data in the selected extent.
Please try using a lower resolution package for the terrain.
I am using the lowest resolution available. Any idea's how to overcome this or what is causing the issue?
Kind Regards,
Steve
I have no known source for these two points.
In a file that was already attached to the terrain model file, I found a suspected line segment that connected the two points at 0 elevation. It's reasonable to suspect that this line was added as a series of spot shots (definitely not break line), but I can't remove that segment from the terrain model because it's not a source for the terrain model.
My next guess was that I might be able to add that line segment as spots, and then remove it again, finally losing those 0 points. That didn't work.
So finally I constructed my own line between the points and took that route again. Still didn't work. Any ideas?
I guess one solution that comes to mind is that I can export this terrain as an XML file, find the rogue points and delete them, and then re-import that file. I'm not sure what fallout that might have, and it's something I'd rather avoid anyway, if I can do it another way.
I'm using Geopak SS4 .878.
My company is making the switch to SS4 (we will eventually have PowerGeopak SS4, for now it is Civil Engineering Suite). I have seen a couple threads on this already, but I first want to make ABSOLUTELY sure that SITE is completely gone and never coming back. Is this correct? This is very unfortunate, because I have built lots of tins with this tool. It seems to me that the only way to build now is to have chains and profiles for every single "would-be" SITE element. You must have different templates for every single scenario you have.
Any suggestions on building ADA-compliant curb ramps? In SITE, I was able to start with the proposed profile, build my curb lines off of it, and then work my ADA ramps in.
I was also able to very easily plot my retaining wall profile sheets by getting the existing ground at the back of wall and proposed ground at face using the profile analysis tool.
I am getting the feeling that the new software is being driven by huge roadway projects with miles and miles of work, however the smaller jobs I work on don't seem to translate. Or am I just missing something?
Any input would be much appreciated!
This is pseudocode for what it looks like the end-condition and target aliasing does:
for each endCondition in endConditionsList:
for each target in targetAlias:
try:
goodTarget = find target
fail:
next target
if goodTarget then break
else next endConditionThis is the pseudocode for what I think it should be (at the user's option, if not across the board):
for each target in targetAlias:
for each endCondition in endConditionsList:
try:
find target
goodEndCondition = endCondition
break
fail:
next endCondition
next targetI have a corridor whose end condition to the right is for a depressed median, and it should be targeting the right lane's surface to the left where possible (namely, fill), but otherwise it should find the existing terrain if it can't find the proposed surface of the right lane. The left lane's template has end conditions in what may be a predictable order, each of them targeting <Active>:
Alias <Active> has two targets: 1) the right lane surface, and 2) the existing surface. I am not using nearest.
What I find is that the template looks first at the EC in priority 1 position. It doesn't find the right lane surface, so it finds the existing surface. End of story.
If I delete the existing surface from <Active>, the EC in priority 1 position fails, so it falls back to priority 2 and priority 3, and finally finds the fill section solution.
What I'm suggesting here is that if I want my corridor to find a parallel roadway's proposed surface in a fill condition before it finds the existing surface in a cut section, it should do that.
The reason I think it should be across the board is because if a user wants their template to find a certain surface, they probably don't care whether it's in a cut section or fill section. They want it to be found. And the fact that the user has the targets listed as he does, the user probably expects the first entry to be the preferred entry across all end conditions, not just for the highest-priority end condition.
Then you'll need a whole lot more documentation than I can easily provide.
But probably the best way to proceed is to think about what you need right now, your primary goal: whether it's lateral construction limits, ditch elevations, or whatever.
Then figure out what all you need in order to get it. Consider the level of precision you need at the moment, as that will tell you whether you need to worry about superelevation. (Superelevation is simple and quick once you know how to do it, but it's another step that you don't already know--assumably--how to do, and if you don't need anything super precise, it might be fine to leave it off.)
You'll almost invariably need an alignment and profile. That's pretty obvious. Unless all you're looking for is the surface of a paved road in space, you'll also need an existing surface (or any other surface to which your cross section will be tying). (That existing surface will need to be set as active in the file where you're creating the corridor.) You'll need to tell Geopak *what* to construct, whether it's a 2-lane road or whatever. (In OpenRoads, the typical section is called a template; the template drop is the application of this template over a range on your corridor. The corridor is a set of one or more template drops.)
You'll need to tell Geopak any special features for deviations from that typical section, like side slopes, clear zone width, pavement width, etc., using one of a fairly decent array of tools at your disposal: for pavement width, either attach graphical elements or assign parametric constraints to establish lateral offset. That sort of thing.
From here, it gets a whole lot more complicated, especially when dealing with local roads and merge and diverge gore areas, etc. I won't even bother.
But I guess I just covered design, and that's not what you were asking about. lol. And now I give up because, as I said at the top, I don't even know where to start, for plans production.