Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
OpenRoads | OpenSite
  • Product Communities
OpenRoads | OpenSite
OpenRoads | OpenSite Wiki Horizontal Alignment Imported from Native into OpenRoads is Not Ruled
    • Sign In
    • -Road and Site Design - Wikis
      • +OpenRoads Designer
      • +OpenRoads ConceptStation
      • +OpenRail Designer
      • +OpenSite Designer
      • +OpenRoads Navigator Mobile App
      • -SS10/SS4/SS3 OpenRoads
        • Platform compatibility
        • +SS4/SS3 Subsurface Utilities Video Clips, TechNotes & FAQs
        • +3D Geometry (SS4)
        • +Analysis & Reporting (SS4)
        • +Basic Settings (SS4/SS10)
        • +Civil Cells (SS4)
        • +Corridor Modeling & Cross Sections (SS4)
        • geopakcom.exe - Entry Point Not Found - PowerGeopak Install Error in Windows 10
        • -General Geometry (SS4)
          • Change Color of Handlers and Manipulators
          • Context Tool Box does not appear for Geometry Elements
          • Curve Widening Table .wid file
          • Delete PI in OpenRoads (SS4)
          • Export Civil Geometry to MX - Halgn,Valgn and Verat Linemode
          • Failed to Persist message when Exporting to Native
          • Feature Not Displayed in 3D Model
          • General Geometry > Export to Native is not adding Verticals to Active Geometry Project
          • Graphic Manipulators Missing on Civil Elements
          • Horizontal Alignment Imported from Native into OpenRoads is Not Ruled
          • How can you delete Horizontal Geometry from OpenRoads? (SS4)
          • How do I create a copy of civil geometry? (SS4)
          • How to Export Corridor Modeling Elements to Native
          • How to set custom exaggeration values for the profile view
          • How to transfer geometry in an ALG file to a GPK file
          • How to use Associate MX Strings function
          • How to Use Create Civil Rule Feature Command
          • Import Geometry error after selecting GPK file "The specified module could not be found. (Exception from HRESULT: 0x8007007E)
          • Import InRoads ALG into OpenRoads (SS4)
          • Input MX geometry from an inp file to OpenRoads
          • Insert PI Into Civil Geometry in OpenRoads (SS4)
          • Key Station
          • Negative Co-ordinates
          • Profile does not export to GPK using Export to Native command or Auto Export in Feature Definition
          • Remove Snap Constraint
          • Two Point Line with Stationing does not show up as Chain in GPK file.
          • Unable to read file, Cannot find geometry importer dll
          • Vertical Alignment Imported from Native into OpenRoads is Not Ruled
          • Vertical Alignment is Not Exported to Native
          • Video : Civil Geometry Export to MX
          • Video : Create ICM
          • Video : Creating OpenRoads geometry and exporting the same to Native MX
          • Video : Difference between Deactivate Reference Rules & Remove Rules in Open Roads Technology
          • Video: How to Edit OpenRoads Stationing Symbology
          • Video: Alignment Annotation
          • Video: Apply Multiple Design Standards to a Single Complex Geometry Element
          • Video: Assigning a Feature Definition to Geometry
          • Video: Civil Geometry Import and Export
          • Video: Complex Transition Between Any Element and Arc - Example Workflow
          • +Video: Geometry Tools Overview
          • Video: How to Remove Civil Rule from Multiple Elements at One Time
          • Video: How to Set Element Information in Open Roads Technology
          • Video: Import Geometry and Changing Symbology/Feature Definition
          • Video: Import Native Geometry into OpenRoads
          • Video: Import Plan Graphics to OpenRoads
          • Video: Introduction to Civil Accudraw
          • Video: OpenRoads Integration with GPK File
          • Video: Reason and solution for element not valid for Tool error & Create Civil Rule Feature
          • Video: Ruling a Profile Imported from Native
          • Why Export to Native
        • +Horizontal Geometry (SS4)
        • +Rail Track (SS4)
        • ReadMe - What's new and revised in SS4 MR3 - Version 08.11.09.903+
        • +Survey (SS4)
        • +Terrain Model (SS4)
        • +Training for OpenRoads commands in InRoads/GEOPAK/MX SS4
        • +Vertical Geometry (SS4)
        • Visual Basic Run-time error '-2147467259 (80004005)' when loading GEOPAK through FDOT workspace
        • Why warning display Create an Unlinked Terrain Model
        • How to launch InRoads/GEOPAK SS10 from ProjectWise CONNECT
        • Print and Print to File Button Not Working
        • Problems Running SS4 VBA in SS10
        • Wiki: How to create a turnout library for specific project as the options available to create new turnout library is disabled ?
      • +GEOPAK Native
      • +InRoads Native
      • +MX Native
      • +OpenRoads SignCAD

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

    Horizontal Alignment Imported from Native into OpenRoads is Not Ruled

    Product(s): InRoads, MX, GEOPAK
    Version(s): 08.11.09+
    Area:  General Geometry
    Original Author: Jacquelyn Pettus, Bentley Technical Support Group

     

    Problem:

    I am attempting to import geometry into OpenRoads using the Import Geometry tool.  However, one of the horizontal alignments is imported but is not ruled.  Why is this alignment not ruled when others are?

    Solution:

    If any of the following conditions are true, the imported geometry will not be ruled:

    If the following is true, then a "too many elements" message is produced:

    • Number of adjacent lines is greater than 20

    If the following are true, then a "too complex message" is produced:

    • First element is a spiral
    • Last element is a spiral
    • Back to back spirals (i.e., double spirals or reverse spirals)
    • Spirals must be tangent to the previous element ( tangential differences must be less than 0.1 seconds or it is consider non-tangent)
    • Spirals must be tangent to the next element (tangential differences must be less than 0.1 seconds or it is consider non-tangent)
    • Single spiral between adjacent circular arcs and the circular arcs are reversing (i.e., back curve to the left and the ahead curve to the right or vice versa)
    • Adjacent elements are not coincident (i.e., delta x less than 0.0001 and delta y less than 0.0001 or it is consider non-coincident)
    • Elements are too short (i.e., length is less than 0.5)
    • Circular arcs with a sweep angle of 180 degrees (i.e., median noses or loop ramps)

     

    • Share
    • History
    • More
    • Cancel
    • Jacquelyn Pettus Created by Jacquelyn Pettus
    • When: Fri, Feb 21 2014 2:44 PM
    • Jacquelyn Pettus Last revision by Jacquelyn Pettus
    • When: Fri, Oct 17 2014 1:30 PM
    • Revisions: 5
    • Comments: 0
    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