(SELECTseries 3) Civil Workspaces Getting Started

(SELECTseries 3) Civil Workspaces Getting Started
Presented by: Chuck Lawson, PE

(SELECTseries 3 ) Civil Workspaces
Bentley-Civil Workspace Excellent for “out of the box experience” Provides an example for developing own workspace Prevents Agencies and Consultants from “starting from scratch”

Bentley-Civil Workspace Included as part of the default install process Default Path for Layered Suite Products C:\ProgramData\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\Projects\Examples Default Path for Power Products C:\ProgramData\Bentley\PowerInRoads V8i (SELECTseries 3)\WorkSpace\Projects\Examples

Accessing the Bentley-Civil Workspace User Examples Project Bentley-Civil-Imperial Bentley-Civil-Metric Interface Bentley-Civil

Suggested Workspace Organization Review the Project Configuration File (PCF File) Layered Suite Location C:\ProgramData\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\Projects\Examples\Bentley-Civil-Imperial.pcf Power Product Location C:\ProgramData\Bentley\PowerInRoads V8i (SELECTseries 3)\WorkSpace\Projects\Examples\Bentley-Civil-Imperial.pcf

Where are the Workspace Settings located? DGNLibs should be used to set the specific requirements for a customized workspace. The Bentley-Civil Workspace showcases the use of DGNLibs to host the settings associated with the completion of a customized workspace.

Civil Configuration Variables…. Bentley-Civil Workspace PCF file shows a great example set MicroStation Help Individual Product Help

Important Configuration Variables CIVIL_CONTENTMANAGEMENTDGNLIBLIST CIVIL_ROADWAY_TEMPLATE_LIBRARY CIVIL_XIN_FILE CIVIL_SURVEY_STYLEFILE CIVIL_CIVILCELLDGNLIBLIST CIVIL_DESIGNSTANDARDSDGNLIBLIST CIVIL_PROJECTSETTINGSDGNLIBLIST CIVIL_CIVILTMDGNLIBLIST CIVIL_CIVILSETTINGS_READONLY CIVIL_SUPERELEVATION_RULES_DIRECTORY

Civil Configuration Variables These civil specific variables should be set or everything in the included dgnlib will show up. Example, features used to create a civil cell will be made available as selectable features to use from the Civil Cell DGNLib if not set. Setting CIVIL_CIVILCELLDGNLIBLIST and pointing to that DGNLib, would then only extract civil cells and nothing more.

Civil Configuration Variables - Example

Features What is a “Feature”?
At it’s simplest, a Feature is anything in your design that represents a real-world entity. Curb and Gutter Asphalt Pavement Manhole Wall Aggregate Base R/W Marker Ditch Fill Slope Etc.

Feature Definitions What is a “Feature Definition”?
Properties used to define how a feature is to be displayed, annotated, computed, etc.. These are normally customized by each organization. These are normally created in advance and propagated across an organization in order to standardize designs.

Types of Feature Definitions
3 types of feature definitions are supported. Point Feature R/W Marker Control Point Iron Pin Linear Feature Curb & Gutter Wall Ditch Surface Feature Existing Ground Aggregate Base Asphalt Pavement

Types of Feature Definitions
Depending on its type, a feature definition will have various properties that are available for definition. Point Linear Surface

DGN Libraries Feature definitions reside in DGN Files/Libraries.
DGN Libraries (optimal) Allows for propagation of standards across an organization DGN Files Can be created directly in DGN file, but this is not the recommended procedure Note: When a feature definition is used from a DGN Library, the feature definition will be copied into the DGN file. This is standard MicroStation functionality (e.g. levels, line_styles, fonts, etc.).

Question How does the software know which specific DGN Libraries contain features? Or does it just read from all of them?

Civil_ContentManagementDGNLiblist
This variable is used to define which specific DGN Libraries are to be used to define your features. If this variable is not set, then all the DGN Libraries will be read and any that contain features will be listed.

Standards Transfer Workflow
DGNLib  Active DGN The first time a new feature, element template, etc. is used from a DGNLib, just like with Levels, that information will be copied into the active DGN file.

Project Explorer Where do I manipulate the properties associated with the workspace entries? Project Explorer: MicroStation's interface for browsing elements in a DGN file. Extended by Bentley-Civil to accommodate specialized civil needs.

Project Explorer Where to control the accessible properties for
Settings > Project Explorer

Project Explorer Feature Definitions are created, modified and reviewed in MicroStation’s Project Explorer application. MicroStation File > Project Explorer > Civil Standards Note: Tab Display Controlled by Settings > Project Explorer

Project Explorer The Civil Standards tab will show you what Feature Definitions are contained in your current file, as well as those in any specified DGN Libraries. Current File DGN Libraries

Creating Feature Definitions
How do I create a Feature Definition? Link To Native (automatic) InRoads – XIN File GEOPAK – DDB File, XML File (Survey) MX – PSS File Manual Creation Combination of both Note: Feature Name MUST be unique

Link to Native (GEOPAK)
Uses Active DDB Creates an actual link back to the DDB file

Categories/Folders in DDB are carried through to Feature Definitions.

Right-Clicking on any feature definition gives you access to multiple options, including the ability to review the properties.

Notice that the Feature Definition is automatically linked back to the native style in the DDB. This is where it would get the symbology properties, annotation properties, etc.

If you wish to override this automatic designation with another selection from the DDB, you can do this by simply selecting another item from the drop down.

Link to Native (InRoads)
Uses Active XIN File Creates an actual link back to the XIN file

Since the XIN has no categories/folders, none are available to be carried through to the Feature Definitions.

However, right-clicking gives you the ability to create categories.

You could then use standard cut/paste techniques to re- organize your feature definitions.

Right-Clicking on any feature definition give you access to multiple options, including the ability to review the properties.

Notice that the Feature Definition is automatically linked back to the native style in the XIN. This is where it would get the symbology properties, annotation properties, etc.

If you wish to override this automatic designation with another selection from your XIN, you can do this by simply selecting another style from the drop down.

Link to Native (MX) Creates an actual link back to a user specified PSS File

Link to Native (MX) Since the PSS has no categories/folders, none are available to be carried through to the Feature Definitions.

Link to Native (MX) However, right-clicking gives you the ability to create categories.

Link to Native (MX) You could then use standard cut/paste techniques to re- organize your feature definitions.

Link to Native (MX) Right-Clicking on any feature definition give you access to multiple options, including the ability to review the properties.

Link to Native (MX) Notice that the Feature Definition is automatically linked back to the native style in the PSS. This is where it would get the symbology properties, annotation properties, etc.

Link to Native (MX) If you wish to override this automatic designation with another selection from your PSS, you can do this by simply selecting another style from the drop down.

Question We mentioned earlier that there are three types of feature definitions; Point, Linear and Surface. When linking to a legacy feature file, how does the software determine what type each feature is?

Surface The DDB does not support any surface properties for feature definitions. All features will be created as either Linear or Point. Linear and Point features can be converted into Surface feature definitions after linking.

Point The following DDB entries will be created as Point types: Any DDB entry that has a “Cell Name” assigned.

Linear The following DDB entries will be created as Linear types: Any DDB entries that are a Default item

Linear The following DDB entries will be created as Linear types: Any Drafting Standard that has any combination of the Lines, Curves, Spirals, Stationing, Parcels or Profiles Drafting Standards enabled

Linear and Point The following DDB items will result in the creation of two feature definitions, a Linear and a Point type. A Default item with a Cell Name assigned.

Linear and Point The following DDB items will result in the creation of two feature definitions, a Linear and a Point type. A Drafting Standard with the Cell name assigned and any combination of Lines, Curves, Spirals, Stationing, Parcels or Profiles preferences enabled.

Linear and Point In this scenario, the Linear feature will maintain the original item name, while the Point feature will be appended with a “-Pnt” suffix.

Linear All styles which have the Geometry Line, Curve or Spiral enabled are given a linear feature definition. All styles which have the Surface setting for 3-D/Plan Display enabled are given a linear feature definition. Point All styles where the Geometry Points is defined are given a point feature definition. Surface All styles that have the Surface Setting for Components enabled are given a surface feature definition.

Names must be unique. As such, feature definitions that span multiple types will be organized as shown in the image below.

Link to Native (MX) MX String dimensions dictate the resulting mapping to Civil Feature Definitions. Linear All Feature strings are given Linear Feature Definitions All Section Strings are given both Linear and Surface Feature Definitions Point All Point String types are given Point Feature Definitions. Surface MX Triangulation.pts stylesets are given a surface feature definitions.

Link to Native (MX) Feature Names must be unique. As such, each Feature Definition may contain multiple Feature Types. Any Surface Definition Automatically maps to an Element Template not the native style.

Link to Survey The process or workflow for linking to the native survey legacy file is the same for all three products.

Link to Survey Right-click on the Feature Definitions tree and select Link Survey Feature Definitions. You will then be prompted to select the appropriate file.

Link to Survey Note the Survey properties will be different as opposed to linking via the non-Survey features workflow. Link to Survey Link to DDB/XIN/PSS

Manual Creation of Feature Definitions
A feature definition can be manually created at any point by right-clicking and selecting the desired option. The properties of the feature definition would then need to be set manually as well.

Best Practice Linking to your legacy style files is intended to be a ‘starting point’ to help you get your feature definitions created quickly. Best practice is to do this once. After the initial linking has been done, any structural changes to the feature definition tree (new features, renaming of features, etc.) should be made directly in the DGN Lib. Note: An exception would be changes to symbology or annotation, which would be made in the legacy style file.

Element Templates In addition to pointing a feature definition back to a legacy style in order to assign display properties, you also have the option of pointing to a MicroStation Element Template.

Jump Start with Civil Workspace
What are “Element Templates”? Element Template – A MicroStation concept which allows preconfigured definitions for symbology and other miscellaneous display of MicroStation elements and civil features.

Element Templates vs. Native Styles
In some situations the Element Template is desirable as opposed to the Native Style Surfaces Feature Definitions used for Existing Terrain Models

In GEOPAK the D&C Payitem Attribute can only be placed if the Feature Definition is pointing back to that DDB Native Style entry. Element Templates do not currently support Payitem Attributes.

Surfaces Feature Definitions used for Proposed Components

Note this is an either/or option. You cannot have both defined. If you try and select both it will ‘disable’ the Element Template and by default use the Native Style.

Properties of Feature Definitions
Let’s first take a look at the individual properties and how they work. Point Linear Surface

Feature Definition > Name Prefix
Found in all 3 types (Point, Linear and Surface) This prefix would be used as the ‘default’ name prefix for any civil element placed using this feature. For Geom. intended to be exported back to native GPK (GEOPAK Only), the COGO naming rules must be followed.

Plan Property Available for Point and Linear features
Defines how the feature is to be displayed in a 2D view Allows for either Native Style or Element Template definition Auto Export (True or False) Auto Annotate (True or False)

Auto Export If set to True, then any geometry elements created using this feature will be automatically exported to the appropriate legacy coordinate geometry database (FIL, ALG, GPK). If set to False, then this export would not occur. ALG FIL GPK

Auto Annotate If set to True, then the horizontal geometry element will be annotated immediately whenever it is created or modified. If set to False, then annotation would not occur. Note: You MUST use a Native Style in order to produce annotation, as the specifications for the annotation are based on the native feature style.

Auto Annotate (GEOPAK only)
For Auto Annotate to function correctly the Auto Export MUST be enabled as well. MicroStation Drawing Scale must be set to a value that matches a value in the DDB Native Style being used.

Auto Annotate (GEOPAK only)
For Auto Annotate to function correctly the Design File Settings > Civil Formatting > Station Settings MUST be changed to the “By Index” setting. This should be set in all GEOPAK customers seed files as the default.

3D Property Found in all 3 types (Point, Linear and Surface)
Defines how a feature is to be displayed in a 3D View. For Point and Linear features, this property allows for either Native Style or Element Template definitions. However, for Surface features, it only allows for Element Templates. Note: For surface features to be available in the template library editor, they must be pointing to an element template.

Linear 3D Appearance Considerations
The 3D linear feature property should consider the color of the rendered surface. For example, a back of curb may be yellow in the 2D plan design, but in the 3D model it only makes sense to have this color match the concrete material assigned in the surface feature assignments through element templates.

Profile Property (Surface)
Defines how a profile cut from a surface is to be displayed in a Profile View (normally existing profiles). Allows for Native Style or Element Template definition No Auto Export Note: No Auto Annotate for Profiles in current version

Profile Property (Surface)
If you use an Element Template, the symbology for the profile is taken from General Settings.

Profile Property (Linear Feature Type)
Defines how a profile with this feature (normally a proposed profile) is to be displayed in a Profile View. Auto Export functionality same as explained previously Allows for Native Style or Element Template definition Note: No Auto Annotate for Profiles in current version

The profile is always in a child/parent relationship with a horizontal geometry element. As such, the feature of the profile will always be inherited from the horizontal geometry.

The profile symbology can be overridden at placement by the specification of an Element Template. After placement, the symbology can be overridden via the assignment of an Element Template in the Element Information dialog.

Profile Feature (Review)
Feature inherited from Horizontal Feature inherited from Surface

Projected Profile Property
Available for Linear feature definitions only When a profile with this feature is projected onto another element, the symbology specified here will be used to display it. Allows for Native Style or Element Template definition

Intersected Profile Property
Available for Linear feature definitions only Defines how a point representing the intersected profile with this feature is to be displayed in a Profile View. Allows for Native Style or Element Template definition

Cross Section Property
Available for Linear feature definitions only Defines how a feature is to be displayed in a dynamic cross section view as well as plans production cross sections Allows for Native Style or Element Template definition

Cross Section Annotation Feature Property Requirement
Required – A linear feature must have a drawn active point on the cross section’s linear features that require annotation.

Question Shouldn’t a Surface feature definition contain a cross section property as well? How will the software know how to display my existing and proposed surfaces on cross sections?

Cross Section View Display
When cross sections are cut, the proposed elements take their symbology directly from the proposed 3D model.

The existing ground symbology is always taken from the 3D Property of the feature definition (which must be an Element Template). For example, here someone has gone into Element Information and changed the triangles to ‘blue’.

Yet the existing ground line displayed in my cross sections is still ‘green’.

That is because the symbology for the existing ground is being taken from the Element Template called out in the 3D property of the feature definition.

Linear Default Settings Property
Available for Linear Feature Definitions only

Automatically Create 3D Elements
If this property is set to True, then this functionality is enabled for this particular feature definition. However, in order for this functionality to actually be applied at placement, the toggle on the Feature Definition Toggle Bar MUST be enabled as well.

Automatically Create 3D Elements
What does this property do? When you place a horizontal geometry element using a feature that has this enabled AND the Create 3D Automatically is enabled on the toggle bar, an existing ground profile and a best fit profile is automatically created for the element being placed. In addition, the best fit profile is made active, creating a 3D element.

Corridor Template If this property is assigned a template, then this functionality is enabled for this particular feature definition. However, in order for this functionality to actually be applied at placement, both the Create 3D Automatically AND the Use Feature Definition Template toggles on the Feature Definition Toggle Bar MUST be enabled as well.

Terrain Model Feature Type
This property specifies how this feature should be treated – as a None, Break Line, Void or Boundary - should this feature ever be used in the creation of a Terrain Model.

Create Template Geometry
Specifies whether the 2D geometry should be created whenever a template containing this feature is used. If True, then the 2D geometry will be drawn. If False, then it will not be drawn.

How does this work? Each point in a template is assigned a feature. This feature either has the Create Template Geometry functionality enabled or disabled.

When a corridor is created, then if the Create Template Geometry is enabled for a feature, then the 2D geometry will be drawn. The resulting geometry is not ruled to the alignment, but it is ruled to the Corridor (i.e. if the Corridor updates the geometry will update as well) Feature = Road_EdgeOfPavement

Survey If a feature is created using the Link Survey Features Definition option, the Is Survey option will automatically be set to True. Otherwise, it will be set to False. This is really a ‘flag’ that enables the software to quickly figure out which features are to be used as Survey Features and which are not.

Survey > Native Style
This is the link back to the native style, which contains all the information required for symbolization and annotation. Note that Element Templates are not allowed for Survey Feature Definitions, only Native Styles.

Survey > Alpha Codes, Numeric Code
The user can specify which Alpha and/or Numeric Codes are to be used to identify this particular feature.

Survey > Default Zone
Allows a user to specify which Zone the feature is to be assigned to.

Survey > Terrain Model Attribute
Specifies which attribute is to be assigned to this feature definition when it’s used in the creation of a terrain model.

Survey In-Depth Look

Surface Defaults Available in a Surface Feature Definition only.
Specifies how the surface is to be treated with regard to earthwork volumes. MUST be assigned prior to the surface feature being drawn and sections being cut. If you assign it later, the surface/model needs to be re-processed and the sections re-cut.

Project Settings What are “Project Settings”? Project Settings:
Customized preferences to be used in the creation of corridor designs and surveys. These preferences can be applied as the defaults for both corridor design and survey creation, or they can be applied at various time increments throughout a project. In addition, these Project Settings can be saved in DGN Libraries and consequently propagated across an organization.

Project Settings Project Settings - Supported Options
Corridor Design Stage Settings Linear Template Design Stage Settings Survey Settings

Project Settings Project Settings – Corridor Design Stages
Template Management Critical Section Inclusion Display Settings Output Settings

Project Settings Project Settings – Template Management
Template Drop Interval Multiplier Used to increase the final template drop value to expedite the corridor processing times. For example, if a designer wants a final design template interval every 10 feet but is working in a preliminary conceptual layout, they may want this number set to 10 to only have cross template drops every 100 feet in their conceptual model. Ultimately, this will process the model up to 10 times faster then the final design stage where the multiplier would be set to 1.

Project Settings Project Settings – Include Critical Sections
Exact usage as in V8i (SELECTseries 2), these settings dictate inclusion or exclusion in the processing of the design corridor. Regarding the horizontal and vertical curve densification, consider turning those on only in the final design stages as they do require considerable additional processing times.

Project Settings Project Settings – Display Settings
Controls the display of the corresponding boundaries and handles of the following: Corridor Template Drop Single Station Edit Template Transition Consider making these “Construction Class” elements in the corresponding required Element Template settings.

Project Settings Project Settings – Output Settings
Controls what is plotted in the 3D model used for rendering and terrain model creation. Best Practice, avoid putting everything in one Project Setting as it makes it difficult to distinguish all the different outputs.

Project Settings Suggested Minimum Corridor Design Stage Considerations Preliminary Design Stage Design Stage Final Design Stage Final Design Stage With Meshes Final Design Stage Top Mesh Only Final Design Stage Bottom Mesh Only Final Design Stage Linear Features Only Final Design Stage Components Only

Project Settings Project Settings – Linear Template Design Stages
Display Settings Output Settings Note: The interval of template drops is set by stroking configuration variables for linear template drops in the workspace startup CIVIL_DEFAULT_LINEAR_STROKING = 10.0 CIVIL_DEFAULT_PROFILE_STROKING = 0.05 CIVIL_DEFAULT_CURVE_STROKING = 0.05

Project Settings Suggested Minimum Linear Template Design Stages
Final Design Stage With Meshes Final Design Stage Top Mesh Only Final Design Stage Bottom Mesh Only Final Design Stage Linear Features Only Final Design Stage Components Only

Project Settings Project Settings – Survey Settings General Settings
Point Settings Linking Code Settings Data File Parsing Least Square Defaults Elements Symbology Terrain Model

Graphical Filters What are “Graphical Filters”?
Used in developing terrain models. Automated way of storing search settings for graphic elements when creating terrain models using 3D elements. A Graphical Filter can be created for each feature (i.e., spots, breaks, voids) for existing or proposed terrain. Graphical Filters can be defined as a Graphical Filter group.

Graphical Filters Example
Uses the Selection Set Concept with Access to Civil Platform Features.

Graphical Filter Groups
A Graphical Filter Group can be created combining multiple individual Graphical Filters. This is done using the Graphical Filter Manager

Design Standards What are Bentley-Civil “Standards”?
Design Standards: Design Standards can be used to maintain required curvature and other alignment checks when performing horizontal and vertical geometric layouts. Provide values for the element creation tools (for example, minimum radius and transition lengths) Check the suitability of complex elements (for example, check for kinks in the alignment) Superelevation Preferences: U.S. method (GEOPAK – Legacy SEP File) International method (MX – Legacy SRL File) InRoads legacy SUP files are not supported in SELECTseries 3

Design Standards Document Link

Setup – Superelevation Calculations
Utilize SEP or SRL files (preferences) Configuration variable points to directory for SEP / SRL CIVIL_SUPERELEVATION_RULES_DIRECTORY SUP files are not supported. In lieu of calculations, importing superelevation from external program (CSV file)

Import File CSV (comma separated values) file
Uses Windows delimiter (generally comma)

Format of CSV File SuperelevationName,Station,CrossSlope,PivotAbout,PointType,TransitionType,NonLinearCurveLength CL_RT1, ,-0.02,RS,NCIN,L,0 (if everything is included) LT-1, ,-0.02,LS (minimal amount)

Supported Formats – Required Data
Superelevation Name (name of lane) o Required. o Links the data to an existing superelevation lane. Station o Units should match design file. o Station equations supported based on the reference alignment. Cross Slope o Formatted as a double value : ±0.0 (i.e. -2% == -0.02) Pivot About o Required. Default Value = 0.0 o Enumerated list : {LS,RS} LS = left side RS = right side o Only pertinent for transition type: parabolic curve or symmetrical reverse curve.

Supported Formats – Optional Data
Point Type § NC, NCIN, NCOUT (Normal Crown) § FS, FSIN, FSOUT (Full Super) § RC, RCIN, RCOUT (Reverse Crown) § LC, LCIN, LCOUT (Level Crown) § U (Undefined) Transition Type § L (Linear) § BRC (Biquadratic Reverse Curve) § PC (Parabolic Curve) § CRC (Cubic Reverse Curb) § PRC (Parabolic Reverse Curve) § SRC (Symmetrical Reverse Curve) Non-Linear Curve Length o Default Value = 0.0. o Only pertinent for transition type: parabolic curve or symmetrical reverse curve.

SE Location of Settings Files in Install
C:\ProgramData\Bentley\Civil\Standards\8.11.9\en\Superelevation SRL SEP

SE Common Functionality of SEP / SRL
Support Imperial / Metric Support station equations Supports linear / parabolic transition methods Resolves overlapping transitions Can be run by any product

SE Comparison Chart for SEP / SRL
SEP (GEOPAK) SRL (MX) Equations / Formulae Basic formulae Supported extensively Multiple lanes w/ different default cross slope Supported Not supported Half Lanes Nominal vs. Actual Lane Widths Adjustment Factors Axes of Rotation / Pivot Methods Centerline/PGL 6 methods Early Start Indicator Constraints

SE Structure of SEP Files
Set of files, only 1 SEP per processing Up to 2 CSV files for “tables” method (none for equation method) CSV files can have any name and are specified in the SEP file Error message if not found – no processing can be done. No paths needed if all in same folder

SE Structure of SRL Files
Set of files, only 1 SRL per processing Up to 8 ASCII files (but 2 are typical) SRL file contains pointers to other files Specific format Lots of comments / notes in file

Superelevation - How to Get Started
Gather current standards for super calculations. Determine current SEP / SRL files. Find most knowledgeable person on super standards, not necessarily a Civil software user. Review comparison chart to determine what’s needed. Using the Excel spreadsheet / preferences doc, determine settings. Set-up and test. (requires Civil software user).

Superelevation Template Settings
Toggle on the Superelevation Flag setting in the point properties of the templates to be used in the corridor design to allow the set point to be selected when assigning the superelevation to the corridor.

Superelevation Workflow
CALCULATE / IMPORT SUPERS CREATE LANES CREATE SECTIONS DYNAMIC EDITING ASSIGN TO CORRIDOR REPORTING

Seed Files Seed File Suggested Edits…
Set DGN File Civil Settings appropriately Set Default Drawing Scale Set default Snap Divisor to 1 Turn off clip volume for all views in view attributes Delete unused fonts in keyin field Set default text style Attach default cell library GEOPAK must change Civil Settings Station Equation to “By Region” for auto annotate to function properly

Level Priorities Consider setting Level Priorities to simplify the graphical process. Can be set to a maximum value of 500 (Highest Priority). By default all levels are set to zero Not needed for all levels Consider high importance items Centerline / Baseline Proposed edge of pavement or shoulder Etc.

Seed Files Seed File Civil Settings…

Seed Files 2D or 3D Design The 2D Model Provides…
Display control Picking control Annotation Plans Production Auto Managed profile and 3D model Familiarity Ease of use 2D Accudraw “Best Practice” – Geometric design in 2D model.

Seed Files Text Scaling MicroStation Drawing Scale:
Sets test size for all new functionality including Auto Annotation, Cross Sections, Survey, etc. InRoads Global Scale Factor: Uniquely controls Auto Annotation text size Does not effect text size in cross sections

Material Assignments Material Assignments Can be set per DGN Level
One material per level Can be set per Element Template Allows for different materials on same level (i.e. Level Name = Pavement) Important for adequate 3D Model visualization

Material Assignments Material Assignments using Level

Material Assignments Material Assignments using Element Templates
“Best Practice”

XIN File XIN File Usage Settings / Database LandXML file which contains feature definitions, associated styles, annotation, and other settings. Used by InRoads, GEOPAK, and MX for all settings relating to cutting, annotating, and computing Cross Sections. Used by InRoads ONLY for storing exported Bentley-Civil Geometry and other Legacy settings.

XIN File Create Cross Sections Settings
Cross Section Sheet Creation Preferences are stored in the XIN file for all platforms. Used to control all settings in XS Sheet creation.

XIN File Annotate XSect. Settings
Cross Section Annotation Preferences are stored in the XIN file for all platforms. Used to control all settings in XS Sheet annotation.

XIN File End Area Volume Settings
Cross Section End Area Volume Preferences are stored in the XIN file for all platforms. Used to control all settings in XS End Area Computations.

Function Key Suggestions
Function Key Ideas Choose None Exits the user from any Civil Command TerrainModel Analyze Point Allows the selection of any alignment or point and provides instant feedback such as station and offset. Dynamically Updates Corridor Templatelibrary Open Opens the template library to explore or edit templates

Template Component Surface Features
Accessing Feature Definitions in Template Components Must be a Surface Feature The Surface Feature must be defined by an Element Template

User Preferences Settings
User Preference Considerations View Options – Civil Customize the look and feel of numerous items relating to geometry manipulation. Manipulator settings Superelevation settings Survey locater Error ellipses Context flyover settings Etc.

User Preferences Settings
User Preference Considerations Operation Resource Cache Suggest increasing in multiples of 1024. Sets the amount of memory, in KB, reserved for resources read from the product resource files and application resource files.

Civil Cells Many engineering workflows include redundant and tedious modeling tasks with similar, but slightly varying parameters. OpenRoads technology offers methods for these “similar but different” designs that ‘capture’ and reuse these design, while easily adjusting their parameters. Model intersections, traffic islands, driveways, field entrances, and a host of other standards with parametric settings by simply placing a “cell.”

Civil Cells What are the problems we need to overcome?
When we draw in a CAD environment, we often find the need to draw the same objects repeatedly. Thus the need in MicroStation to have some type of functionality that allows us to do this. MicroStation cells provide this functionality. We can define and then save these objects in a cell library. And whenever we need a particular object, we just look for it in our library and place it, eliminating the need of drawing the same object repeatedly.

As Civil Designers we find ourselves designing the same ‘Standards Driven’ geometric configurations over and over but often only with minor modifications.

Manual creation is a time consuming process, fraught with potential errors ‘Standards Driven’ does not mean ‘Standard’ in practice Traditional wizards are often too restrictive, they might make the simple easy but they make the complex impossible as they only allow what’s been programmed into them Simply maintaining the graphical representation of these configurations in a standard MicroStation cell would not be sufficient. We must be able to carry the engineering intelligence behind the configuration forward in order to reuse it and modify after placement.

Civil Cells What is a “Civil Cell”?
OpenRoads Technology + MicroStation Cell At it’s simplest it can be thought of as a ‘Visual Macro’ for repeated use of pre-configured 2D and 3D geometric layouts that maintain design intelligence.

Civil Cells Civil Cells
Used as a mechanism to preconfigure commonly used complex geometric layouts. Commonly stored in DGNLib files for reuse across multiple projects. Sometimes useful to store directly in an active DGN file for use in that single location. The civil cell will contain horizontal geometry and can also contain vertical geometry.

Civil Cells Civil Cells DGNLib Organization
Create and use Civil Cells from active DGN file (Project Specific Based) Store one Civil Cell per DGNLib Store multiple Civil Cells per DGNLib in a single DGN model Store multiple Civil Cells per DGNLib using multiple DGN models

Civil Cells - Use Cases ‘Simple’ 2D geometry layout right through to ‘full’ 3D layout Examples Junctions Driveways Median Cross Overs Roundabouts Ponds Ramps Parking bays Building pads Traffic Management layouts

Placing Civil Cells Selection from distributed DGNlib
Requires base Geometry for References and where defined Optional References Direction control Corridor to Clip - optional

Manipulating Civil Cells
Geometry Area Templates Linear Templates Clipping Template Drops Target Aliasing

Civil Cell Contents Geometry Requires Geometry references
Rules to Children Elements Direction and location of reference elements are used to try and find best placement solution Manages metric / imperial conversion automatically Snaps Civil Accudraw constructions maintained Good snaps – end point, intersection, perpendicular, tangent, center, mid point (used carefully) Bad snaps – XY, Nearest

Civil Cell Contents Terrain
Created from Graphics - this is a Ruled Terrain and so updates automatically Can be created with an open boundary Temporary construction terrains made from geometry allow draping on the surface where required

Civil Cell Distribution
Area Templates Depth components about origin Can only be applied to Terrains Only forms Vertical edge Allows overlay components Limitations Linear features are not created

Civil Cell Contents Linear Templates
Design Stage (different from corridor) Corridor objects – sub set of Corridor Parametric Constraints Point Controls Unsupported corridor objects Clipping Reference External Reference Note anything with a station is not supported in Civil Cells

Civil Cell Creation – Getting Started
Use Control Geometry Civil Accudraw Construction Elements Consider Keeping the 2D Think about your approach to Corridor Templates Plan ahead Build small sub components and test Consider how it might be modified Consider Element Naming Consider user prompts

Civil Cell Distribution
DGNLib Defined by cfg variable CIVIL_CIVILCELLDGNLIBLIST \WorkSpace\Projects\Examples\Bentley-Civil-Metric.pcf CIVIL_CIVILCELLDGNLIBLIST = $(_USTN_PROJECTDATA)/dgnlib/Civil_Cells_Metric.dgnlib

Questions

(SELECTseries 3) Civil Workspaces Getting Started

Similar presentations

Presentation on theme: "(SELECTseries 3) Civil Workspaces Getting Started"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

(SELECTseries 3) Civil Workspaces Getting Started

Similar presentations

Presentation on theme: "(SELECTseries 3) Civil Workspaces Getting Started"— Presentation transcript:

Similar presentations

About project

Feedback