I am modifying one of our alignments in the DC Manager by adding a 60 scale. It allowed me to add the scale and set everything the way I want except it will not allow me to change the offset in small tick label or large tick label. The offset is stuck on 0.60 and it will not allow me to change it to anything else. Any ideas?
↧
SS3 Geopak Offset won't update in DC Manager
↧
How do I add an element template to a feature definition?
I am trying to understand what goes into generating the necessary feature definitions starting from my legacy ddb file. I have linked my ddb into a dgnlib file, and I created an element template to define the level/symbology for a particular feature, but I cannot add my element template to a feature definition. What am I missing? I am working in PowerGEOPAK SS3 08.11.09.722 (Backing up a step, I need to define element templates and then use them in order to get the proper level/symbology associated with a feature, is that correct?)
↧
↧
Microstation Solids and Meshes in Openroad Cross Sections
Hello,
I am using Geopak 08.11.09.722 Civil Tools --> Corridor Modeling to view and create cross sections. Using the view cross section tool, all Microstation meshes, solids, and surfaces in the 3d file appear in the cross section model view. Using the create cross sections tool, none of these show up, only the corridors or terrain models. Is this the correct behavior? How do I get other 3d modeled items, such as 3d Geopak Drainage nodes and pipes to appear in the cut cross sections.
Thanks
Rick
↧
Project Defaults in OpenRoads SS3
In the SS2 version of the Inroads product users were able to set project default locations for different file types so that when you opened or saved a particular file the program would default to the exact location, saving the time required to browse to a directory location time and again. In SS3 this does not seem to be the case, specifically for the "Open Template" dialogue box. Is there a way to have this dialogue open to a default location in SS3 similar to SS2?
I know there is a variable which you can set to have the program always default to a particular ITL file. While this appears to work on the surface we have run in to issues when working in a ProjectWise environment.
Marc
Inroads 722
↧
SS3 Power InRoads – Terrain Conflicting Points Report
I am using the Terrain Conflicting Points Report dialog (please see screen capture below). The conflicts have a padlock which does not allow me to make changes to the elevations from this dialog. When I right click to change the elevations, these options are greyed out. Are property settings for these greyed out options hard coded in the software and cannot be changed or is there a configuration variable or setting that can be set in order to edit the elevations of these points from this dialog instead of having to go back to the original source file to make the edits?
↧
↧
Set Active Feature Definition with VB
I am looking for a simple key in or VB example to set the Active Feature Definition. The only thing I can come up with is this confusing string:
"CIVILCMD SETVALUE FeatureDefinition=Bentley.Civil.Geometry.Model.LinearEntity2dInPlan, Bentley.Civil.Geometry.Model.3.0, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4bf6c96a266e58d4|E_Terrain_Contour_Major>~Lin|False ".
When I try to break the above sting apart and run it without all the garbage in it, PowerGEOPAK crashes.
There should be an easier way to code this in a custom VBA such as:
CadInputQueue.SendCommand "ActiveFeatureDef=E_Terrain_Contour_Major"
Thank you for your assistance I greatly appreciate it.
↧
OpenRoads Do Not Construct Feature Definition
hi
I guess it may be simple but need your expertise.
Corridor with all pavement components, desired 3D output is to have in Default-3D model component meshes and linear features but just for the top of proposed roadway. Is there a way to set up FD that 3D linear features will not be created? I didint defined element templates for linear and #D features but lines are created and put on Default level with default symbology. for now my workaround is to put these DNC (do not construct) lineear features on a specific level and turn the display of that level off.
aby tip would be helpful.
Thanks.
Adam
↧
SS3-Open Roads-Survey Data>Filters
Is there any information on Survey Data>Filters in Open Roads? I created one to try and filter my Property features from my surface features but nothing seems to happen regardless of whether the filter is checked or unchecked.
↧
Does use of native ddb vs. element templates for feature definitions affect processing time?
As I get set up for SS3 I am wondering if linking to the ddb means that there will always be some processing time to "go find" the information in the ddb when trying to apply a feature definition to my graphics. Is the time required for that greater than what would be needed to access the information via element templates. In my testing, it has seemed to take time for a ddb-generated feature definition to actually appear to be applied to my graphics. (PowerGeopak 08.11.09.722)
↧
↧
InRoads SS3 - What Controls Axis Text Height?
Hello,
Maybe I've got a case of the stupids, because I thought I had this working.
What Controls the height of the Axis text when creating cross sections?
I thought it was the Text Scale Factor in PROJECT OPTIONS > FACTORS, but that doesn't seem to be working.
Normally I set my cross section axis text to be .12 and use the Text scale factor to set the final text height.
Right now, all my axis text is cominig out .12, regardless of Text Scale Factor.
Thanks,
Tom F.
↧
What is your best way to set up sheets for Proposed Cross Sections?
Wondering if anyone had a great way to do this. I have about 10,000 feet of cross sections that I need to show. I am going to put 4 cross sections per sheet. My cross sections are going to be spaced every 100' Normally the way I would do this is just to xref my cross section sheet 4 different times and pop them into the space I want. They will update automatically if things changed and all is good. However, I have been informed that down the road, we may run into problem areas where we might need to show a cross section every 50'. So I am looking for the best way to set this up so if I have to insert 50' cross sections half way through my sheets, I am not having to pick up and move 50 references between various sheets to accomodate this. Or perhaps the way I am doing it is the only way? Thanks for any input ya'll can provide.
Microstation V8i Select Series 3
Bentley GEOPAK V8i (SELECTseries 3) 08.11.09.493 for Microstation V8i on Windows x86
OS: Microsoft Windows 7 Profressional
System Model: HP Z820 Workstation
System Type: x64-based PC
ProcessorL Intel(R) Xeon(R) CPU E5-2631 0 @ 2.30GHz, 2301 Mhz, 6 Core(s)
(RAM) 8.00GB
CAD User for 2 years
↧
InRoads XSL Reports...
Is there a way to get the leading zeros to show up? For example, we need to show the leading zero in the delta angle for curves.
I'm currently exporting to Excel in order to paste the tabled data into a DGN. Even if there's a way to show the leading zeros in Excel, that would help.
↧
InRoads XSL Report: Negative values...?
I'm getting negative values for the Tangent, Middle Ordinate and External Distance for one of my curves. What gives?
EDIT: Nevermind, I was working rather quickly, and I didn't even pay attention to the Delta.
↧
↧
OpenRoads and ProjectWise Workflows issues
I have some problems with OpenRoads files on Projectwise after revising documents. Basicli it refers to a file with superelevation definition.
for the simplicity i will limit project size here just to show the crux of problem. There are following files:
Terrain.DGN
Geometry.DGN
Superelevation.DGN
Corridor.DGN.
Terrain.DGN is referenced to Geometry.DGN and Geometry.DGN is referenced to Corridor.DGN with live nesting (just to have terrain in corridor.dgn)
Geometry.DGN is referenced to Superelevatin.DGN and Superelevation.DGN is referenced to Corridor.DGN
The problem occurs when I change state of files on ProjectWise or revise these files. Then I open Corridor.DGN and I am asked by PW dialog to switch reference files to active version. When Corridor.DGN is oppened it reveals that superelevation is not applied to corridor anymore. I tried to assign superelevation to a corridor again but got message that Superelevation has unresolved reference (Before revising files it was working fine, carriageways had been superelevated). I can not even reproces corridor and when trying I get message about unresolved superelevation references.
Then I go to superelevation.DGN file and on oppening I get PW dialog to switch geometry.DGN reference to active version. It looks that this superelevation is ready to be assigned to a corridor. Then I check-in superelevation.dgn file and open Corridor.DGN file - now I can assign superelevation to a corridor with no issues.
I would like to avoid opening Superelevation.DGN file to switch its references to active version just to have my corridor working well. I have two ideas how to avoid that:
1) keeping superelevation definition in the Geometry.DGN file;
2) Change referencing setup to the following: Terrain.DGN->Geometry.DGN->Superelevation.DGN->Corridor.DGN
The first one seems to be fine but is it a good practice? I imagine that when geometry is ready to be shared no one should open that file while there still might be a need to edit superelevation and adjust it to corridor requirements.
Second option will not fit to scenarios where there is no superelevation and we try to have a compn referencing setup for all scenarios.
do you have any other ideas? Why we get this message that Superelevation has unresolved references when trying to reprocess corridor? Is it beause superelevation.DGN references have to be switched to active version first?
Thanks in advance.
Adam
↧
PowerCivil Point cloud import failed
When I try "Create Terrain From Point Cloud" the process fails. See attached image. The oroginal file is .pts and I imported it in Descartes and got a .pod file that I am now working with. What could be my problem?
↧
Feature Definition in referenced files - Civil Data is not displayed
I have a dgn with corridor definition in 2D model. Default-3D model is created. When I display Element Information for a 3D linear feature I get info on Feature Definition that is assigned to that linear object, abot corridor, etc - all civil related data.
now I reference that Default-3D model to other dgn (Master 3D file) - I display element Information for the same 3D linear feature and get no information on Feature Definition, corridor, etc. Moreover even Feature Name is missing. Only the symbology and level names are propagated.
Why? I want to use graphical filter by Feature Definition to create terrain from selected linear features, eg. to create terrain of carriageway and display contours.
Please see screenshots proving what stated above. I don't believe it is WAD. Is is user fault or software related issue.
Default-3D model:
And now the same feature, from the same Default-3D model but referenced to Master DGN:
↧
GEOAPK-BOREHOLE OPEN ALERT
↧
↧
Geopak Drainage Labeler error
I am trying to use the Drainage Labeler but the dialog box shrinks and I can't expand it. See screencaps below.
I actually have to Save and reopen Drainage to get the dialog box back open to be able to chose a different style. Anybody else having this problem?
Power GEOPAK V8i SS2 v08.11.07.615
↧
GEOPAK Project manager dialogue not appearing.
I have a coworker who cannot get the GEOPAK project manager to display. She can access Road Tools and the dialogue box is not hidden behind any other windows. as always with strange occurrences, it was perfectly fine the day before.
Thanks
↧
Difference in a .e and .x criteria file?
Hi all,
Just wondering the difference between an .e and .x criteria file for geopak. I am still learning Geopak myself, been using it for a couple weeks, but one of my PMs uses old .e criteria files from our Dot's 2004 files. I noticed that their 2012 release has .x file extension instead and was wondering what the difference was.
↧