Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
MicroStation
  • Product Communities
MicroStation
MicroStation Wiki Global Origins
    • Sign In

    • -MicroStation Wiki
      • +Learning Tips
      • -MicroStation
        • +3D Printing - MicroStation
        • +Animation - MicroStation
        • +Archive / Backup - MicroStation
        • +Base Geometry - MicroStation
        • +Batch Processing - MicroStation
        • +CONNECT Advisor - MicroStation
        • CONNECT Integration - MicroStation
        • +CONNECTION Client
        • +Cells - MicroStation
        • +Change Tracking - MicroStation
        • +Configuration - MicroStation
        • -Coordinate Systems - MicroStation
          • +ACS - Coordinate Systems - MicroStation
          • +General - Coordinate Systems - MicroStation
          • -Geographic - Coordinate Systems - MicroStation
            • Converting GCS from ED50-IGN.ES-UTM30 to ETRS89-UTM30N gives wrong results
            • Create and Edit a User Coordinate System
            • Creation of Local GCS
            • Enable Bing Maps Background Map in View Attributes
            • Export KML in Cartesian coordinates
            • +Geo-Coordination With MicroStation
            • Geographic (longitude/latitude) coordinate readouts in
            • Global Origins
            • Helmert Transform
            • How do you redefine the Coordinates of a DGN, and re-designate the GO?
            • How to assign a coordinate system to multiple design files in a batch
            • How to configure/add grid shift files in CONNECT edition
            • Insert Longitude and Latitude Coordinates in a DGN file with Geographic Coordinates Systems in meters
            • Reprojecting to a new Geographic Coordinate System
            • The NAD83 datum is missing for the UTM projection when assigning a coordinate system.
            • Unable to load/create dialog item of type 'IconCmd', id = 29 from dialog "MDGSHOOK"
            • Where can I see the new Australian Geographic Coordinate System GDA2020
            • Why are there differences between the new GDA2020 Australian coordinate system and the previous MGA94?
          • +Global Origin - Coordinate Systems - MicroStation
          • Global Positioning - Coordinate Systems - MicroStation
        • +Curves - MicroStation
        • +Custom Linestyles - MicroStation
        • +DGN - MicroStation
        • +DWG - MicroStation
        • +Database - MicroStation
        • +Detailing Symbols - MicroStation
        • +Dimensions - MicroStation
        • +Documentation & Help - MicroStation
        • +Drawing Aids - MicroStation
        • +Exception - MicroStation
        • +FAQ - MicroStation
        • +Feature Based Solids Modeling - MicroStation
        • +File Access - MicroStation
        • +GUI - MicroStation
        • +General - MicroStation
        • +Graphics Display - MicroStation
        • +Groups - MicroStation
        • +Hardware / Input Devices - MicroStation
        • +Import/Export - MicroStation
        • +Installation - MicroStation
        • +Interchange - MicroStation
        • +Interference - MicroStation
        • +Internationalization - MicroStation
        • +Levels - MicroStation
        • +Licensing - MicroStation
        • +Manipulation - MicroStation
        • +Markup / Redline - MicroStation
        • +Measure - MicroStation
        • +Mesh - MicroStation
        • +Models - MicroStation
        • +Multi-Lines - MicroStation
        • +OLE - MicroStation
        • +Other - MicroStation
        • +Parametrics - MicroStation
        • +Patterning - MicroStation
        • +Point Cloud - MicroStation
        • +Printing - MicroStation
        • +Programming - MicroStation
        • +Project Navigation - MicroStation
        • +Properties - MicroStation
        • +RSS Feeds - MicroStation
        • +Reference - MicroStation
        • +Security - MicroStation
        • +Selection - MicroStation
        • +Settings - MicroStation
        • +Sheet Composition - MicroStation
        • +Solids - MicroStation
        • +Standards - MicroStation
        • +Surfaces - MicroStation
        • +Tables - MicroStation
        • +Text - MicroStation
        • +UI Customization - MicroStation
        • +Units - MicroStation
        • +View - MicroStation
        • +Visualization - MicroStation
        • Welcome Page - MicroStation
        • +Accreditation - MicroStation
        • +i.Models - MicroStation
        • +ProjectWise Integration
        • +Raster - MicroStation
    • +Administration Wiki
    • +Annotations Wiki
    • +Bentley View Wiki
    • +MicroStation PowerDraft
    • +Programming Wiki
    • +Visualization Wiki

     
     Questions about this article, topic, or product? Click here. 

    Global Origins

    Document Information

    Document Type: FAQ

    Product(s):  MicroStation V8 2004 Edition and previous

    Version(s):  All

    Original Author: Bentley Technical Support Group

    Legacy Document Number:  6314

    How do I check or query to see what the Global Origin is set to in a design file?

    GO=? reports the global origin, but also activates the command. If you hit reset to get out of the command it will actually change the global origin command. if you click a data point after keying in GO=? you will change the global origin.

    Use GO=$ to check the value of the global origin without activating the command.

    NOTE: Thanks to Kevin van Haaren for his comment regarding this command.

    How do I set the global origin?

    The global origin is set by using the key-in: GO=,, (without the use of the <> symbols). After the coordinate values have been entered into the key-in window and the key-in has been accepted, there are two methods in setting the origin.

    If a point is selected in a design file, this is referred to as a "Monument Point" in which the point that is selected will now have the coordinate value that was entered for the Global Origin.

    If you select reset, the global origin will be set to the lower left corner of the V7 design plane allthough you are in a V8 file. This is essentially labeling the lower left corner of the V7 design plane with the coordinate value that was entered using the GO=,, key-in. Note: The is not necessary in a 2D file.

    Why is the global origin set to the lower left hand corner of the V7 design plane when reset is performed to set the origin value?

    In order to maintain the correct element location during the upgrade process from V7 to V8, the origins would need to coincide with the same value. Therefore, the V7 design plane would allow this to be maintained.

    When I check the global origin value by keying in GO=?, why is the value displayed the opposite value than what I had originally keyed in? For example, I set the global origin to 1,1,1, but the GO=? returns the values of -1,-1,-1.

    When the global origin is queried, the value that is displayed in the Message Center is the value where the point 0,0,0 is located with respect to the lower left corner of the V7 design plane. If the global origin is set to 1,1,1, the point where 0,0,0 is located is at location of -1,-1,-1 from the lower left corner of the design plane.
    GO=? reports where 0,0,0 is, with respect to the Bottom corner of V7 deisgn plane.

    Can the global origin exist off the design plane?

    Yes, the global origin can exist off the design plane

    If I change my global origin, will my elements be located in the same coordinate location?

    If the global origin is changed, the elements will remain in the same location, however, the coordinate location will be changed. In order for the elements to show the correct coordinates, the elements would need to be moved into the correct location with respect to the global origin.

    The data does not move, but the coordinates do.

    When I create a new design file using the delivered seed file seed3d.dgn in MicroStation, why is the global origin set to 214748.3648, 214748.3648, 214748.3648?

    By default, the delivered seed files are set to the center of the design plane or design cube. This center location is marked as 0,0,0. When the GO=? key-in is used, the GO= -214748.3648, -214748.3648, -214748.3648 is reported back since 0,0,0 is located at the coordinate value from the lower left corner of the V7 design plane.

    Global Origin comes delivered at the center of design.

    How do I reset the global origin to the center of the design cube so that 0,0,0 is at the center?

    In order to reset the global origin to the center of the design cube, the following key-in can be utilized: GO=0,0,0;xy=0,0,0|uor. The uor after the pipe symbol (shift+\) stands for "Units of Resolution".

    Will different global origins between design files cause problems when the design files are referenced together?

    When design files are referenced using the "Coincident" method, the design files are stacked on top of each other regardless of what the global origins are. The elements alignment will be incorrect unless each design file has the same global origin and the design elements are in the correct coordinate location with respect to each file.
    If the reference files are attached using the "Coincident-World" method, the reference files will align to the correct location according to the coordinate values of the elements with respect to the origin of the active file.

    Is the ACS Triad an indicator of where the Global Origin is located?

    No, the ACS Triad can be in a different location than the Global Origin. The ACS Triad cannot be reliably used as an indicator of the Global Origin's location.

    When I save my V8 file to V7, why is the Global Origin being shifted and my elements appear to be scaled when I open the newly created V7 file?

    Since the V8 design plane is approximately 2 million times larger than the V7 design plane, the elements in the V8 file can exist outside the V7 design plane. In order to fit all elements onto a smaller design plane when saving the file to V7, the elements that fall outside of the working area need to be scaled and possibly shifted causing the elements to be smaller and may end up having a different global origin due to the shift.
    If you see cases where this is happening, be sure to examine the messages in the Message Center immediately after Save to V7 has been performed on the V8 file. More details will be presented to these actions.

    If the Global Origin can be moved, is the design plane also being shifted?

    By setting the working units and the resolution for a design file, you are setting a finite size for the design file. Therefore, the design plane (2D) or design cube (3D) in a design file cannot be moved or shifted. However, changing the global origin in turn moves the point 0,0,0 on the design plane. This allows a point on the design plane to be explicitly set to a particular coordinate value based upon the shifting of the Global Origin.

    See Also

    Product TechNotes and FAQs

    MicroStation Desktop TechNotes and FAQs

    External Links

    Bentley Technical Support KnowledgeBase

    Bentley LEARN Server

    Comments or Corrections?

    Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

     

       

    • FAQs
    • GO
    • MicroStation V8
    • FAQ6314
    • Global Orign
    • Share
    • History
    • More
    • Cancel
    • Dan Koval Created by Bentley Colleague Dan Koval
    • When: Fri, Sep 6 2013 1:19 PM
    • Jon AR Last revision by Jon AR
    • When: Fri, Jun 26 2015 7:03 AM
    • Revisions: 4
    • Comments: 3
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies