1 / 153

(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

sitara
Download Presentation

(SELECTseries 3) Civil Workspaces Getting Started

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. (SELECTseries 3) Civil WorkspacesGetting Started Presented by: Chuck Lawson, PE

  2. (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”

  3. (SELECTseries 3 ) Civil Workspaces • 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

  4. (SELECTseries 3 ) Civil Workspaces • Accessing the Bentley-Civil Workspace • User • Examples • Project • Bentley-Civil-Imperial • Bentley-Civil-Metric • Interface • Bentley-Civil

  5. (SELECTseries 3 ) Civil Workspaces • SuggestedWorkspace 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

  6. (SELECTseries 3 ) Civil Workspaces • 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.

  7. (SELECTseries 3 ) Civil Workspaces • Civil Configuration Variables…. • Bentley-Civil Workspace PCF file shows a great example set • MicroStation Help • Individual Product Help

  8. (SELECTseries 3 ) Civil Workspaces • 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

  9. (SELECTseries 3 ) Civil Workspaces • 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.

  10. (SELECTseries 3 ) Civil Workspaces • Civil Configuration Variables - Example

  11. 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.

  12. 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.

  13. 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

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

  15. 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.).

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

  17. 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.

  18. 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.

  19. 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.

  20. Project Explorer • Where to control the accessible properties for Project Explorer? • Settings > Project Explorer

  21. 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

  22. 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

  23. 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

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

  25. Link to Native (GEOPAK) • Categories/Folders in DDB are carried through to Feature Definitions.

  26. Link to Native (GEOPAK) • Right-Clicking on any feature definition gives you access to multiple options, including the ability to review the properties.

  27. Link to Native (GEOPAK) • 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.

  28. Link to Native (GEOPAK) • 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.

  29. 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?

  30. Link to Native (GEOPAK) • 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.

  31. Link to Native (GEOPAK) • Point • The following DDB entries will be created as Point types: • Any DDB entry that has a “Cell Name” assigned.

  32. Link to Native (GEOPAK) • Linear • The following DDB entries will be created as Linear types: • Any DDB entries that are a Default item

  33. Link to Native (GEOPAK) • 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

  34. Link to Native (GEOPAK) • 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.

  35. Link to Native (GEOPAK) • 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.

  36. Link to Native (GEOPAK) • 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.

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

  38. 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.

  39. 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

  40. 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.

  41. 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.

  42. 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.

  43. Element Templates • 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.

  44. 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

  45. Element Templates vs. Native Styles • 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.

  46. Element Templates vs. Native Styles Surfaces Feature Definitions used for Proposed Components

  47. Element Templates vs. Native Styles • 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.

  48. Element Templates Caution • When developing the Features Definition DGNLib, and an Element Template is assigned to a Feature Definition Property, the selected Element Template will get copied from its DGNLib to the active Features DGNLib. • Upon completion of the Features DGNLib edits, make sure to manually delete the Element Template entries copied over to the Features DGNLib. This of course assumes the Element Templates are stored in a separate DGNLib versus the Feature definitions.

  49. Element Templates for Terrain Models • Special Element Template properties must be setup to control the display of terrain model entities.

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

More Related