Our Levels and Naming Conventions

KHA-SD Roadway Levels

The configuration and reference source for the roadway levels is the roadway.dgnlib in M:\CADD\CA\SD\Road\ustn\config\_kha_customizations.  This library is automatically loaded in MicroStation unless you are not using the Roadway Configuration.  All other lists and translators are derived from this file (and can fall out of date).

Note: if a change is made in the roadway.dgnlib the following changes must also be made

Here is the level list (note: it's manually created from the dgnlib and can be out of date).  Please provide comment on prefixes and content.  In particular if you have something that should require a new level please let me know.

CalTrans 63

We have the CalTrans63 defined as a dgnlib, which in many cases is automatically attached to the active design file (this depends on the active kha client configuration).

Here is a list of the proposed levels as they map to the CalTrans 63 (it may be out of date).  A better source for this information is the MicroStation Translation file EPS_to_CT.csv

The CalTrans Level source is http://www.dot.ca.gov/hq/oppd/cadd/usta/caddman/english/2.4_drawing_data_levels_e.pdf

Level Naming Convention

Naming Convention Issues

In the 12/14 meeting it was agreed that the Levels

• should not have the CalTrans numeric prefix,
• should have the numeric Prefix in the Description (allowing "CalTrans grouping" by clicking the Description header in the Level Manager and Level Display forms).

Here is a list of the proposed levels as they map to the CalTrans 63.

What's the purpose of Levels, anyway?

• Organize data
• Facilitate work
  • Be able to turn off irrelevant information (see only the stuff you need to see)

Goal: maximize productivity without adding too much complexity.

Note:  the length of the level name (including prefixes and suffixes) matters in that the Level controls often only show the first twenty or so characters.

Level Hierarchy

A "prefix hierarchy" paralleling our product logic should be established.

Some "suggestions" and tips

Text Levels will be designated with a "_Text" suffix.

If there are a couple of options and one is far more common, both do not need explicit naming.  Example:

• "drain_area"
• "drain_area_predevelopment"
• "drain_area_text"

Note that "drain_area" implies the more common "drain_area_postdevelopment".  Question: does predevelopment need it's own text level or are both okay on the same level?

In Progress and Needing Input

No Plot levels: how many and where?

Top Level Prefixes

Condition:  Since most of what we do is proposed, we'll not have a Proposed prefix.  Other conditions warrant a prefix: "x" will prefix Existing Levels (and InRoads objects).  Do we need a prefix for as-builts or can this condition be segregated by file?

Note: when working with InRoads there is often a need to have existing-condition objects displayed properly within a "proposed" .dgn.  Thus, the need for the

List of Prefixes (.xls)