Top Level:

Roadway Environ

KHA-SD Help Group Policy SD Config Client Management CAD Info & Help Projects Site Map

Peer Level: Up News Roadway Environ Config Tasks ustn Architecture Brown Bag List v7 Projects v8 Projects QA/QC Vision Changes Log Sharing the Config Admin Issues

Child Level:
Up
EPS Status
Impact
Plan 4 Superset
Config Lists
EPS - Levels
Xin Superset
Plot Plan

San Diego's Custom Roadway Environment

(formerly the KHA CalTrans Enhanced Productivity Superset).

12/21/07:

  • We got a Roadway Level Library (it's automatically attached already)
  • We got an InRoads Preference file that conforms to it
  • We have preliminary inter-client translation tables for MicroStation
  • We're working on plotting

I've got a preliminary rollout of the EPSuperset going.  Full details on the status page.  Feel free to bang on it and provide me feedback

The leveling is the most volatile part of this.  The sooner we stabilize the convention and get a good "initial stable list" the sooner we can set up the plotting and the translation files.

Preliminary setup of Translation .csv's. Note: there's a lot of detail remaining (bylevel to specified color. etc)

The Roadway Configuration (Superset) pen tables are at M:\CADD\CA\SD\Road\ustn\resources\plotting\roadway_superset.

I have an initial, untested multi-environment CalTrans Dropout Pen Table (CT_dropout_eps.tbl).  Please test it.  This may be the "seed" for the other variations.

What does it all mean? 

Click here for an explanation of what's different today than last week.


What do we want to call it?

EPS has the buzzwords that management funds, but what do we want to call what essentially be the Roadway Group's working environment?  Send in your suggestions.

In the meantime, I may refer to following the Roadway Group Configuration plan as Taking the High Way.  Again, voice your concern by emailing a better suggestion.

What is it: 

it's KHA SD Roadway group standard environment designed to

  1. dramatically Enhance Productivity and Quality Control throughout the long, iterative design process
  2. plot transparently and port easily to the "CalTrans 63 v8" MicroStation standard.

What's wrong with 63 levels? 

63 levels ain't enough (actually, many are reserved, so it's less than 63).  Some examples of the ambiguity of Caltrans 63:

  • buildings and fences share a level
  • ETW's, Shoulders, and Sidewalks share a level (for most InRoads cleanup work, you want to work only with shoulders or only with ETWs; easily confusable now).
  • Level 22 Misc. Construction Detail is something of a catchall, lot's of stuff
  • Level 60 is for Nongeo Data.  Read: a giant bucket for everything profile, section and a whole lot more
  • Everything drainage is on two levels.
  • Sound walls have a level but retaining walls do not.

What will we be able to do with the Enhanced Productivity Superset?

  1. be able to visually and programmatically differentiate different things (this is absolutely huge for productivity speed and the elimination of ambiguity (Quality Control).
  2. integrate very easily with other local and national Kimley Horn and national standards (technically, the CalTrans
  3. easily adopt the new CalTrans v8 standards when they become available

 

Technical Details

How

  • Levels
    • Designing the Enhanced Productivity Superset (beyond CalTrans 63)
    • Managing the Superset
      • A second .dgnlib for the extra level attributes
    • Conversion Procedures

Site Map       Contact Jeff Martin with comments/concerns.        KHA San Diego Transportation Group.                    this page last edited: 2008-01-17 16:26