MICROSTATION ROADWAY DESIGN SEED Design/CADD/Microstation/CADD Manual/0 · PDF...

Click here to load reader

  • date post

    06-Feb-2018
  • Category

    Documents

  • view

    219
  • download

    0

Embed Size (px)

Transcript of MICROSTATION ROADWAY DESIGN SEED Design/CADD/Microstation/CADD Manual/0 · PDF...

  • MICROSTATION ROADWAY DESIGN SEED FILES

    October 7, 2013 General Information

    Introduction

    ACS (Auxiliary Coordinate System) - A FIX for V8i Microstation coordinate labels.

    Selecting Seeds Files for Creating Project Files

    State Plane Coordinate Zones

    Projects that Cross the Zone Line (Located in both the West and East Zones)

    Reviewing the Properties of the Seed File

    Design History

    English Seed File Parameters

    Intergraph Type 56 Element (Coordinate Projection System) for TerraShare and GeoMedia

    Levels in Seed Files

    Metric Seed File Parameters

    The SEED File DGN Environment

    Microstation V8 DGN File Format

    DGN Working Units

    Resolution Settings

    Setting the Global Origin

    View Groups

    View Orientation

    Coordinate Readout

    Saving DGN File Settings

    DWG Files

  • A History of Roadway Designs Working Units

    Research Information (The Survey Foot Unit)

    General Information

    Introduction

    When you create a DGN file, you are actually identifying a seed file to be used as a template for the DGN file. The new DGN file is actually a copy of another files which we call the seed file.

    Via the seed file, any parameters that are operator dependent, e.g., Locks, views, snaps, etc., can be set for any file you create in the future. These include any parameters that can be saved by using the SAVE SETTINGS command.

    Seed files do not (necessarily) contain elements, but, like other DGN files, they do contain at least one default model, settings, and view configurations. Having a seed file with customized settings frees you from having to adjust settings each time you create a new DGN file. To provide consistency, Roadway Design has created SEED files that you must use when working on a MDOT projects.

    The following two design seed files are used for most design work. There will be exceptions to this rule, but you will be notified as to when you need to use other seed templates. The two primary seed files are identical except that each have separate Geo-Coordinate systems attached to define either the state plane coordinate zones that they will work in.

    The design files also contain a special element type. This "Type 56 Element" is a "non-graphical" element that is inserted in the design file to define the survey zone or coordinate system the area is located in. It defines were the design area is located when used in specific GIS applications used at MDOT (i.e., TerraShare & GeoMedia). For more detailed information on zones, see the official MDOT Survey Manual. SEEDE.DGN - 2D, Mississippi East, State Plane Coordinate System. SEEDW.DGN - 2D, Mississippi West, State Plane Coordinate System.

    As mention above, we also have two 3D seed design files that contain the same Type 56 element. They are used only when a 3D files necessary during the design process. Such as with models and contours. SEEDEZ.DGN - 3D, Mississippi East, State Plane Coordinate System. SEEDWZ.DGN - 3D, Mississippi West, State Plane Coordinate System.

    In addition, another type of GIS coordinate system has been applied to these four design files. This coordinate system is applied using Microstation's Geographic Coordinate System tool and can be used inside of Microstation to align other coordinate systems to our seed coordinate systems. The following graphic shows these settings:

  • design files. XSSEED.DGN - traditional 2D Seed File for Cross Sections.

    A newer cross section seed file is now available that is configured to be used when working in Geopak software with Open Roads Technology. This file does not have the different working units and instead matches the normal seed files.

    XSSEEDCIVIL.DGN - Geopak Civil 2D Seed File for Cross Sections.

    ACS (Auxiliary Coordinate System) - A FIX for V8i Microstation coordinates labels.

    All design files that were created in the V8i version of Microstation prior to June 16, 2008 using the RWD seed files contained a bogus ACS coordinate system. Some users may encounter this if the file was created during the period that V8i was installed until the time that the fix was installed after June 16, 2008.

    The problem that was found was in how V8i applied a unnamed Auxiliary Coordinated System (ACS) to each view in each seed file. This unnamed ACS was creating bogus coordinate system readout for some commands. Most notably the Label Coordinate command will place incorrect coordinates.

    YOU ARE NOT REQUIRED to fix the ACS unless you want to use a command such as "LABEL COORDINATE". If you encounter bogus coordinates using this command you can use the fix below:

    Manual Fix Instructions are as follows:

    If you click on the command UTILITIES > AUXILIARY COORDINATES a dialog box will open that shows you the current ACS and the settings for the current active view. For example, you may see something similar to... View 1: Unnamed ... and some bogus numbers after that). What you want to see in the X and Y fields with the numbers 0 (zero). You can manually fix by right-clicking on the line and choose the option (RESET TO GLOBAL). This should set the numbers back to zero and this will fix the bogus coordinates when using the Label Coordinate command, but only the active view that was selected. You must tag another view and make it active to check and fix any bogus ACS numbers. You have to do this same set of steps to fix each opened view. If you have any un-opened views, you have to open them and do this for them also.

    Selecting Seed Files For Creating Project Files

    To create new design files from these seed files you will be using the FILE > NEW options in Microstation. The workspaces must be configured correctly so that the proper or most appropriate seed file template is displayed before the new file name is input and accepted.

    Roadway Design supplies you with the proper workspaces. See the INSTALLATION & SETUP Chapter for more information on workspaces.

  • When you start up Microstation with the proper workspace selected, it will default to the correct seed file. You must know which zone your project is located in so you can start up with this proper workspace selected.

    State Plane Zones For Mississippi

    On the next page is a county map showing the dividing lines between the East and West State Plane Zones in Mississippi:

  • By knowing the county that your project is located in you can use the map above to determine which zone your project is located in.

    Projects that Cross the Zone Line (Located in both the West and East Zones)

    On occasion a project will cross the zone dividing line. When a project is located in both the West and East Zones the District Engineer or Surveyor in charge will determine which zone the project will be placed in and then document this in the CONTROL NOTE for that project. The control note is a cell that is placed and filled-out in the a CONTROL.DGN file or in the TITLE SHEET design file.

  • The picture below shows an example of a GPS CONTROL NOTE. The example shows in BLUE were you can find the zone listed.

    Reviewing the Properties of a Seed File

    Without special software you cannot check to see if the Intergraph zone header or type 56 element is located in the seed design file (needed for GeoMedia and TerraShare). For this reason these design file have had file "PROPERTIES" inserted that can viewed from within Microstation. To see these properties in Microstation. Select FILE > PROPERTIES and go to the Summary Tab. This information will show which zone the file was created. If this is blank then the file cannot be used with the Intergraph software listed above. Below is an example of this property information:

  • Design History

    Design History allows a record changes to the design file to be saved inside the design file itself. Normally, history is not on by default, but has now been initialized (turned on) in our design seed files.

    Note: The design history will cause a design file to be slightly larger in size, because it must save a

    record of changes. To control the behavior of Design History, certain workspace configuration environment variables

    are being used. They are shown below:

    MS_DESIGN_HISTORY_COMMIT_ON_SAVE = 2 MS_DESIGN_HISTORY_COMMIT_ON_CLOSE = 2 MS_DESIGN_HSITORY_COMMIT_ON_MODEL_SWITCH = 2

    Each of these variables are set to automatically commit design file history to the file when saving a file, switching models, closing a file, or exiting the file. The value of 2 means that it will not prompt for a description. These variables do not exclude the user from making commits with descriptions on their own accord.

    Anyone who is not using Roadway's Workspace or do not have the above variable set will have to commit the design file changes when exiting, saving, or closing a design file.

  • English Seed File Parameters

    SEEDE.DGN & SEEDW.DGN

    The following parameters are given to document Roadway Design's (English units) seed file parameters for our standard seed files (seede.dgn & seedw.dgn). Critical Settings are listed in italics and should not be changed.

    Coordinate Readout Working Units View Attributes Format: master units -- linear units --

    Accuracy: 0.1234 Master units: feet (ft) Constructions - on in all views Sub units: Custom (tn) Dimensions - on in all views -- Custom Units -- Data fields - off ins all views

    Angle Readout Master: Use Standard, feet (ft) Clip Volume - off in all views Format: DD MM SS Sub: Define, 10 (tn) = 12 in. Grid - off in all views

    Mode: Bearing -- Advanced Settings -- Lev