Understanding features
This presentation is the property of its rightful owner.
Sponsored Links
1 / 91

Understanding Features PowerPoint PPT Presentation


  • 38 Views
  • Uploaded on
  • Presentation posted in: General

Understanding Features. Presented by: Derricke Gray. Understandin g Features.

Download Presentation

Understanding Features

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Understanding features

Understanding Features

Presented by: Derricke Gray


Understandin g features

Understanding Features

  • Now that features live in a DGN environment, it is paramount to learn how they are used in the new OpenRoads technology to identify, name, and symbolize designs to meet an organization's standards. This presentation is meant to familiarize you with this new functionality.

  • At the end of this training session, an assessment will be given. We will review all assessment questions and answers to see what you have learned.


Learning objectives

Learning Objectives

After this presentation you will be able:

  • Identify the valid feature types

  • Link Civil Features to legacy style files

  • Understand how to use DGN Libraries to setup and control civil features


Features

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

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

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 definitions1

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

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

Question

How does the software know which specific DGN Libraries contain features?

Or does it just read from all of them?


Civil contentmanagementdgnliblist

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.


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 explorer1

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

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

Link to Native (GEOPAK)

  • Uses Active DDB

  • Creates an actual link back to the DDB file


Link to native geopak1

Link to Native (GEOPAK)

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


Link to native geopak2

Link to Native (GEOPAK)

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


Link to native geopak3

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.


Link to native geopak4

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.


Link to native inroads

Link to Native (InRoads)

  • Uses Active XIN File

  • Creates an actual link back to the XIN file


Link to native inroads1

Link to Native (InRoads)

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


Link to native inroads2

Link to Native (InRoads)

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


Link to native inroads3

Link to Native (InRoads)

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


Link to native inroads4

Link to Native (InRoads)

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


Link to native inroads5

Link to Native (InRoads)

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


Link to native inroads6

Link to Native (InRoads)

  • 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

Link to Native (MX)

  • Creates an actual link back to a user specified PSS File


Link to native mx1

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 mx2

Link to Native (MX)

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


Link to native mx3

Link to Native (MX)

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


Link to native mx4

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 mx5

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 mx6

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.


Question1

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?


Link to native geopak5

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.


Link to native geopak6

Link to Native (GEOPAK)

  • Point

    • The following DDB entries will be created as Point types:

      • Any DDB entry that has a “Cell Name” assigned.


Link to native geopak7

Link to Native (GEOPAK)

  • Linear

    • The following DDB entries will be created as Linear types:

      • Any DDB entries that are a Default item


Link to native geopak8

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


Link to native geopak9

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.


Link to native geopak10

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.


Link to native geopak11

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.


Link to native inroads7

Link to Native (InRoads)

  • 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 enabledare given a surface feature definition.


Link to native inroads8

Link to Native (InRoads)

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


Link to native mx7

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 mx8

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

Link to Survey

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


Link to survey1

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 survey2

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

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

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

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.


Element templates1

Element Templates

  • A MicroStation functionality which allows preconfigured definitions for display of MicroStation elements and civil features.


Element templates vs native styles

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


Element templates vs native styles1

Element Templates vs. Native Styles

Surfaces Feature Definitions used for Proposed Components


Element templates vs native styles2

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.


Properties of feature definitions

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

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.


Plan property

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

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

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

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.


3d property

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.


Profile property surface

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 surface1

Profile Property (Surface)

  • If you use an Element Template, the symbology for the profile is taken from General Settings.


Profile property linear feature type

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


Profile property linear feature type1

Profile Property (Linear Feature Type)

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


Profile property linear feature type2

Profile Property (Linear Feature Type)

  • 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

Profile Feature (Review)

Feature inherited from Horizontal

Feature inherited from Surface


Projected profile property

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

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

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


Question2

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

Cross Section View Display

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


Cross section view display1

Cross Section View Display

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


Cross section view display2

Cross Section View Display

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


Cross section view display3

Cross Section View Display

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

Linear Default Settings Property

  • Available for Linear Feature Definitions only


Automatically create 3d elements

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 elements1

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

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

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

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.


Create template geometry1

Create Template Geometry

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


Create template geometry2

Create Template Geometry

  • 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

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

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

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

Survey > Default Zone

  • Allows a user to specify which Zone the feature is to be assigned to.


Survey terrain model attribute

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.


Surface defaults

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.


Assessment

Assessment

1. Which of the following is not a valid feature type?

  • Point

  • Pipe

  • Surface

  • Linear

    Answer – b) Pipe

    2. The option to link civil features to a legacy style file is found under which tab in Project Explorer?

  • Survey

  • Civil Model

  • Civil Standards

    Answer – c) Civil Standards

    3. True or False: Civil_ContentManagementDGNLiblist is the configuration variable that is used to point to the DGN Library containing features.

    Answer – True


Understanding features1

Understanding Features

Presented by: Derricke Gray


  • Login