Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Future consideration
Created by Guest
Created on Feb 1, 2023

Introduce the concept of seperate model containers to control data much better

In MX we had the concept of models that allowed users to very quickly and efficiently control feature display, select specific features and perform extensive automation of almost all functions.

Without this functionality in ORD, users a either stuck with all data from all models being in the same "bucket" where feature lists include multiple features with the same name and automation is difficult/impossible. Even use of Reference name is troublesome because the user may have multiple references with the same filename in different paths, etc.

OpenBridge Bridge containers essentially has this concept with its Bridge object containers, where each container is activated by the user when needed.

Example applications could include:

  • Ability to script selection of specific elements by feature name (or by wildcards) for automation of drawing production, data exports, reporting, etc.

  • Ability to script geometric constructions, eg. offset geometry creation, station offset points, etc.

Reference logical name could perhaps be the way to associate a "model name" that would be used for this (with it set to dgn name by default), however it would limit this to per file functionality. Perhaps Named Groups may function better if there was a dialog to access this information for referenced data.

Civil Product Used OpenRoads Designer, OpenRail Designer
  • Guest
    Reply
    |
    Feb 1, 2023

    Not quite, because we wouldn't have 5 versions of all corridor templates that use different versions of the same Feature Definition, eg. Road 1 edge of Pavement, road 2 edge of pavement, etc. The feature definition list would be endless. We need a way to seperate certain elements into different buckets for unique identification and control in my opinion.

  • Guest
    Reply
    |
    Feb 1, 2023

    Can this not be accomplished through the development of the workspace? Creating additonal Feature Defs/Symbology. Utilization of individual levels for elements.