InRoads Management Technologies

The primary InRoads management technologies are:

 Feature Styles

Feature Styles are Object Types.  When we define a Feature Style in InRoads, InRoads can then use the words and object names that we humans use.  We should have a Feature Style for every object type that we want to track in InRoads. 

For example, let us assume that our new boss has a fresh MBA and wants us to track “widgets” in our project.  We can create a Feature Style in InRoads so that whenever an object is, in fact, a widget, we can tell InRoads through a variety of commands that the object is a widget.  Later in the workflow, as we are using evaluation tools, InRoads can tell us when we’ve come across a widget.

The InRoads Administrator should have defined a broad array of Feature Style.  The end user should only have to create new Feature Styles if something unusual, new or unanticipated needs to be tracked for a project.  The InRoads Administrator should be notified unless the new Feature Styles will be unique to the project.

Named Symbology

Named Symbologies are a list of definable, named, CAD settings presets.  Unlike [command] Preferences they are not uniquely connected to a form.  Any often-repeated symbology setting should be defined as a Named Symbology (as time permits). 

Typically, governing agencies have CAD graphic symbology requirements.  An existing sewer pipe may have to be displayed in green on Level “underground_sewer” (or 22 in MicroStation/J), with a weight of 3, with a dashed linestyle.  A Named Symbology called “existing sewer” can be created with those settings.  Once defined, users can select “existing sewer” when specifying the symbology for an existing sewer pipe.

Named Symbologies can and should be used in command Preferences.  In fact, not using Named Symbologies in command Preferences (that is, setting individual values for each component of an object’s display properties) is very bad technique and makes conforming to standards very difficult.  Companies having multiple clients’ standards will find managing Preference files much easier if they have used Named Symbologies throughout the InRoads commands settings.

Named Symbologies should be created when repeatedly specifying or changing symbology settings.  In a well-managed environment, end users should seldom have to repeatedly change the same settings.  A preference should have been created after a few iterations.  Named Symbologies are important when it directly corresponds to a physical object type (Feature Style!) or pervades the software (“screened line” or “Title Text”). 

Command Preferences

Preferences involving Named Symbology wherever possible is the best way to manage symbology automatically.  Please see the Exploring Geometry chapter of Exploring InRoads, the Stationing Section for a thorough review of Preferences with Commands.

Managing Preference Sets across Many Commands.

A Preference Set stores settings for a particular form or command.  Every command has a Preference Set called “default”.  All Preference Sets are stored in the Preference file with the command name and Preference Set Name.

Themes of Preference Sets having like characteristics can and should be created by saving Preference Sets throughout the program with the same name.  A common example of varying characteristics by theme is for Existing and Proposed symbology or other settings.  Another example is using separate Preference Set themes for different client agencies.  For example, Florida DOT has different symbology requirements and design criteria than CalTrans or the City of San Diego .  Segregating Preference Sets is possible through naming conventions.  Naming the Preference Set with a consistent and intuitive prefix or suffix allows improved quality control.  In additional, InRoads can automatically load a particular theme depending on the project (InRoads calls these “Preferred Preferences”).