Understanding Features

1. Understanding Features Presented by: Derricke Gray

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

20. Link to Native (InRoads) • Since the XIN has no categories/folders, none are available to be carried through to the Feature Definitions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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